incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Sukalac (JIRA)" <j...@apache.org>
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 01:05:33 GMT

    [ https://issues.apache.org/jira/browse/CB-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13415827#comment-13415827
] 

Eric Sukalac commented on CB-479:
---------------------------------

After having tried to create a new project in 2.0RC1, I'm a little bit confused over the structure
here. At least when I ran the command-line tools, it created a subproject within my new project
labeled "CordovaLib.xcodeproj" and it is rendering the index.html within that sub-project
. Is that the expected behavior or should the www/index.html be the one being rendered?
                
> iOS Upgrade Guide: Add upgrade path for existing project(s) on how to replace "cordova.framework"
by "cordova subproject"
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CB-479
>                 URL: https://issues.apache.org/jira/browse/CB-479
>             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
faster.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message