- 26 Dec, 2014 40 commits
-
-
Marius Rackwitz authored
-
Marius Rackwitz authored
Same for underlying host_requires_framework
-
Marius Rackwitz authored
As pointed out by @neonichu.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
Fixes the fix in f1a88a4c491a3732bac6df04d7204b8a68034d55.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
This reverts commit 4d7f71bf77bcfe914e9d39d7ff53fab192e9aefd.
-
Marius Rackwitz authored
Contains the duplicated logic from AggregateXCConfig#generate and PublicPodXCConfig#generate.
-
Marius Rackwitz authored
If there are localized resources in a user target, which are referenced in a source build phase, then this caused a crash, because not all valid destination types of the relation PBXBuildFile#file_ref were handled.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
With static libraries and CocoaPods `#import "…"` and `#import <…>` could be used to import the local headers in "$PODS_ROOT/Headers/…". With frameworks the compiler automatically discovers public headers of the linked frameworks, so we have to ensure that we pass the `-iquote` flag for each framework pointing to its embedded headers. Otherwise this will led to errors because either the `#import "…" won't be discovered at all or they will be seen as different and the compiler will fail with duplicate symbols.
-
Marius Rackwitz authored
[Refactor] Extracted #pod_targets_for_build_configuration from AggregateTarget#pod_targets_for_build_configuration
-
Marius Rackwitz authored
-
Marius Rackwitz authored
Make CONFIGURATION_BUILD_DIR and FRAMEWORK_SEARCH_PATHS depend on this instead of double set the value to this constant.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
… to opt-in to frameworks.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
The value was resolved to 'Pods/Pods', before but correct for the user's target. Because the PODS_ROOT build setting is defined in the aggregate xcconfig, which is shared between the aggregate target and the user's target, we have to overwrite the value in the embedded settings in the Pods project's aggregate target.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
The aggregate target's product isn't really needed, so it isn't copied into the app bundle to not clutter and expose details of the build process. `dyld` is trying to link it at runtime, as the aggregate framework is linked to the user's target to trick Xcode, so that it concludes there is target dependency without the need to declare a literal target dependency, which implies that we would need to add a subproject and add the reference to a target, which is newly created on each run of `pod install`, which would cause again undesirably changes to the user's project.
-
Marius Rackwitz authored
-
Marius Rackwitz authored
To reduce code duplication
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
-
Marius Rackwitz authored
So that the OSX Example App for AFNetworking actually runs
-
Marius Rackwitz authored
-