incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Grieve (JIRA)" <>
Subject [jira] [Commented] (CB-479) iOS Upgrade Guide: Add upgrade path for existing project(s) on how to replace "cordova.framework" by "cordova subproject"
Date Tue, 17 Jul 2012 13:21:33 GMT


Andrew Grieve commented on CB-479:

The only thing that is required out of the sub-project is the CordovaLib static library. The
www directory within the sub-project can be ignored. Probably we should create a separate
xcode project file for the CordovaLibApp and CordovaLibTests so that this is less confusing
(I'll try to get to this later today).

The steps I took to convert an existing framework-based cordova project to the new format:

1. Delete the reference to cordova.framework from the navigator. This will also remove it
from all targets.
2. Add the CordovaLib.xcodeproj as a sub-project (right-click on nav, "Add Files", select
3. Add CordovaLib to the "link with libraries" build phase of your app target
4. Add -all_load to OTHER_LDFLAGS of your target
5. Add CordovaLib's VERSION file to the main bundle's resources (I'm not sure if this will
be required when using the release candidate)
> iOS Upgrade Guide: Add upgrade path for existing project(s) on how to replace "cordova.framework"
by "cordova subproject"
> -------------------------------------------------------------------------------------------------------------------------
>                 Key: CB-479
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Docs, iOS
>    Affects Versions: 1.6.0
>         Environment: IOS XCODE MAC
>            Reporter: Emile khattar
>            Assignee: Shazron Abdullah
>            Priority: Minor
>             Fix For: 2.0.0
> If you already created a cordova .framework project using the cordova template in xcode
and you would like to move into a subproject based solution a manual is needed to make it
> Tips from a personal experience:
> - Unlink the cordova framework
> - Un-install cordova framework to make sure the migration went well (then re-install)
> - unset this variable "CORDOVA_FRAMEWORK=YES" from the build settings
> - grep for "#ifdef CORDOVA_FRAMEWORK" in the plugins code to make sure that you are importing
the files correctly.
> - Empty the value of "framework search paths" in the build settings 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message