http://0xc0.de/LibComponentLogging
http://github.com/aharren/LibComponentLogging-configure
(Auto-)configuration for http://0xc0.de/LibComponentLogging.
$ ./lcl_configure --help
(Auto-)configuration for LibComponentLogging, version 0.1.3
Usage: lcl_configure [<options>] <type> [<folder>]
Options:
--[no-]colors (Don't) use colored output.
--[no-]verbose (Don't) be verbose about created/modified files etc.
--help Print this usage message.
--version Print the version.
Types:
plain Create configuration files for a plain installation.
pod Create configuration files for CocoaPods-managed dependencies.
Update the CocoaPods specs repository to get the latest LibComponentLogging pod specs, or install the work versions / drafts of new pod specs as an additional CocoaPods specs repository via pod repo add:
$ pod repo add lcl https://github.com/aharren/LibComponentLogging-CocoaPods-Specs.git
Cloning spec repo `lcl` from `https://github.com/aharren/LibComponentLogging-CocoaPods-Specs.git`
Create a Podfile, e.g.
platform :ios, 8
pod 'LibComponentLogging-Core'
pod 'LibComponentLogging-LogFile'
pod 'LibComponentLogging-qlog'
Then, run pod install which will download and install the pods:
$ pod install
Analyzing dependencies
Downloading dependencies
Installing LibComponentLogging-Core (1.3.3)
Installing LibComponentLogging-LogFile (1.2.2)
Installing LibComponentLogging-qlog (1.1.1)
Generating Pods project
Integrating client project
Then, run lcl_configure pod to create the lcl_config* files:
$ lcl_configure pod
lcl_configure 0.1.3
Creating configuration file 'lcl_config_components.h'
Creating configuration file 'lcl_config_logger.h'
Creating configuration file 'lcl_config_extensions.h'
Using LibComponentLogging-Core (core)
Using LibComponentLogging-LogFile (LogFile logger)
Creating configuration file 'LCLLogFileConfig.h' from template 'Pods/LibComponentLogging-LogFile/LCLLogFileConfig.template.h'
[!] Configuration file 'LCLLogFileConfig.h' needs to be adapted before compiling your project, e.g. adapt '<UniquePrefix>'
Using LibComponentLogging-qlog (qlog extension)
lcl_configure analyzes the Pods folder and the Podfile.lock file and creates the required lcl_config* files based on the configured pods.
Based on the Podfile above, the following files are created:
lcl_config_components.h:
/*::lcl_configure:begin::*/
/*::lcl_configure:end::*/
lcl_config_logger.h:
/*::lcl_configure:begin::*/
#include "LCLLogFile.h"
/*::lcl_configure:end::*/
lcl_config_extensions.h:
/*::lcl_configure:begin::*/
#include "qlog.h"
/*::lcl_configure:end::*/
LCLLogFileConfig.h:
configuration file for LibComponentLogging-LogFile
Whenever you change the Podfile and that change is related to LibComponentLogging, you can run lcl_configure pod again and lcl_configure will update the lcl_config* files. lcl_configure will only touch the managed /*::lcl_configure:begin::*/.../*::lcl_configure:end::*/ sections inside the lcl_config* files.
Update the CocoaPods specs repository to get the latest LibComponentLogging pod specs, or install the work versions / drafts of new pod specs as an additional CocoaPods specs repository via pod repo add:
$ pod repo add lcl https://github.com/aharren/LibComponentLogging-CocoaPods-Specs.git
Cloning spec repo `lcl` from `https://github.com/aharren/LibComponentLogging-CocoaPods-Specs.git`
Create a Podfile including LibComponentLogging and ResKit, e.g.
platform :ios, 8
pod 'LibComponentLogging-Core'
pod 'LibComponentLogging-LogFile'
pod 'LibComponentLogging-qlog'
pod 'RestKit'
Then, run pod install which will download and install the pods:
$ pod install
Analyzing dependencies
Downloading dependencies
Installing AFNetworking (1.3.4)
Installing ISO8601DateFormatterValueTransformer (0.6.0)
Installing LibComponentLogging-Core (1.3.3)
Installing LibComponentLogging-LogFile (1.2.2)
Installing LibComponentLogging-qlog (1.1.1)
Installing RKValueTransformers (1.1.0)
Installing RestKit (0.23.1)
Installing SOCKit (1.1)
Installing TransitionKit (2.1.0)
Generating Pods project
Integrating client project
Then, run lcl_configure pod to create the lcl_config* files:
$ lcl_configure pod
lcl_configure 0.1.3
Creating configuration file 'lcl_config_components.h'
Creating configuration file 'lcl_config_logger.h'
Creating configuration file 'lcl_config_extensions.h'
Using LibComponentLogging-Core (core)
Using LibComponentLogging-LogFile (LogFile logger)
Creating configuration file 'LCLLogFileConfig.h' from template 'Pods/LibComponentLogging-LogFile/LCLLogFileConfig.template.h'
[!] Configuration file 'LCLLogFileConfig.h' needs to be adapted before compiling your project, e.g. adapt '<UniquePrefix>'
Using LibComponentLogging-qlog (qlog extension)
Using RestKit (un-embedded RestKit/RK)
Creating configuration file 'Pods/BuildHeaders/RestKit/lcl_config_components.h'
Creating configuration file 'Pods/BuildHeaders/RestKit/lcl_config_logger.h'
Creating configuration file 'Pods/BuildHeaders/RestKit/lcl_config_extensions.h'
Creating configuration file 'Pods/BuildHeaders/RestKit/LCLLogFileConfig.h'
Rewriting file 'Pods/RestKit/Vendor/LibComponentLogging/Core/lcl_RK.h'
Rewriting file 'Pods/RestKit/Vendor/LibComponentLogging/Core/lcl_RK.m'
lcl_configure analyzes the Pods folder and the Podfile.lock file and creates the required lcl_config* files based on the configured pods.
lcl_configure detects an embedded variant of LibComponentLogging inside a pod -- RestKit in this case -- and automatically "un-embeds" it: all references of the embedded variant of LibComponentLogging will be replaced with a reference to the one which is provided via the Podfile. This way, RestKit log components will be integrated into the central lcl_config_components.h file and RestKit will also use the logging back-end which is configured by the Podfile.
Based on the Podfile above, the following files are created:
lcl_config_components.h:
/*::lcl_configure:begin::*/
#define _RKlcl_component _lcl_component
#include "Pods/RestKit/Code/Support/lcl_config_components_RK.h"
#undef _RKlcl_component
/*::lcl_configure:end::*/
lcl_config_logger.h:
/*::lcl_configure:begin::*/
#include "LCLLogFile.h"
/*::lcl_configure:end::*/
lcl_config_extensions.h:
/*::lcl_configure:begin::*/
#include "qlog.h"
/*::lcl_configure:end::*/
LCLLogFileConfig.h:
configuration file for LibComponentLogging-LogFile
Whenever you change the Podfile and that change is related to LibComponentLogging, you can run lcl_configure pod again and lcl_configure will update the lcl_config* files. lcl_configure will only touch the managed /*::lcl_configure:begin::*/.../*::lcl_configure:end::*/ sections inside the lcl_config* files.
The LibComponentLogging-pods CocoaPods pod spec can be used to automatically download lcl_configure to your project, e.g. create the following Podfile:
platform :ios, 8
pod 'LibComponentLogging-Core'
pod 'LibComponentLogging-LogFile'
pod 'LibComponentLogging-qlog'
pod 'LibComponentLogging-pods'
After running pod install, lcl_configure will be available at Pods/LibComponentLogging-pods/configure/lcl_configure, e.g. you can run
Pods/LibComponentLogging-pods/configure/lcl_configure pod
to create/update the lcl_config* files.
You can install lcl_configure as a post_install hook in your Podfile:
platform :ios, 8
pod 'LibComponentLogging-Core'
pod 'LibComponentLogging-LogFile'
pod 'LibComponentLogging-qlog'
pod 'LibComponentLogging-pods'
post_install do |installer|
system 'Pods/LibComponentLogging-pods/configure/lcl_configure pod'
end
This way, lcl_configure is automatically run by pod install etc. and your lcl_config* files get updated automatically.
Copyright (c) 2014 Arne Harren ah@0xc0.de
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.