In addition to the standard Release and Debug configurations, the application I am developing has an Adhoc configuration used for special test builds. Frames built next to it in the workspace do not have this configuration, because their behavior is not configured for ad-hoc assemblies. Therefore, when a workspace is created for ad-hoc, the products are divided into:
$BUILT_PRODUCTS_DIR(which has a prefix Adhoc)$BUILT_PRODUCTS_DIR/../Release-iphoneosor $BUILT_PRODUCTS_DIR/../Release-iphonesimulator, depending on what we are building for now.
It’s easy enough to get this working with library and frame search paths, adding $(BUILT_PRODUCTS_DIR)/../Release-$(PLATFORM_NAME)to these settings. At this point, my application works correctly, but does not work at the "Embed Framework" step.
My frames are added to the application project with the location BUILT_PRODUCTS_DIRand relative path of only their name.
This question is similar, but it only works for static libraries that do not require this step - I use frameworks.
If there is a better way to handle this, let me know, but I don’t want to push the user configuration up into the frames, because some of them may be ultimately open, and the details of our internal process in this case does not matter.
user4691305
source
share