incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (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 17:33:33 GMT


Shazron Abdullah commented on CB-479:

Unfortunately, this is how Xcode works - it pulls in all targets in all your sub-projects
as well and lists it in the schemes dropdown, and it appears it selects by default the first
target in the list(sorted alphabetically ascending), which would be CordovaLib, for a new

It appears this is the case - if I create a project called "Aaa", it selects that at startup

What we need to do (2.1.0 timeframe?) is to separate out the test app CordovaLibApp and the
unit tests as Andrew suggested - but CordovaLib will still be there in the Scheme dropdown
of course. 
> 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