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

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

[~agrieve] thanks, I'll give these steps a shot later today. 

I think I was (and still am) confused over why the index.html within 
CordovaLibApp was the one being shown in the emulator when I ran a brand new 
install from the command line. Meaning I could completely wipe out the 
index.html in the www folder of my actual project and the emulator would still 
say "Hey, it's Cordova" (pulling the index.html from the subproject)
                
> 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

        

Reply via email to