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

Andrew Grieve commented on CB-5520:
-----------------------------------

I've done quite a bit of work with .xcconfig files in the past.

There's 4 layers of inheritance:
1. Xcode Defaults
2. Project .xcconfig
3. Target .xcconfig
4. Target settings (what we're using now)

Each layer can inherit from the above via $(inherted), but you can't append or 
inherit from settings on the same level.

For this reason, I think it makes sense for us to provide a Target .xcconfig, 
so that users can set their own settings on either side of it (2 & 4).

For an upgrade path, I think it'd be great to have the update script do some 
pbxproj munging to:
1. Add the .xcconfig
2. Delete *all* settings that we set (or maybe everything except PRODUCT_NAME?)

Failing this, we could just have the update script fail with a message saying 
"Recreate your project"



> Should we add "DEBUG=1" to "Preprocessor Macros"->"Debug" ?
> -----------------------------------------------------------
>
>                 Key: CB-5520
>                 URL: https://issues.apache.org/jira/browse/CB-5520
>             Project: Apache Cordova
>          Issue Type: Wish
>          Components: iOS
>    Affects Versions: 3.2.0
>            Reporter: glmnbeyond
>            Assignee: Shazron Abdullah
>            Priority: Minor
>              Labels: core
>
> I created a helloCordova project via Cordova CLI, and added some debug info 
> to native code:
> DLog('This is a debug info');
> But the debug info is never outputted.If I use  ALog, the info can be 
> outputted, so I think it probably has something to do with the "DEBUG" macro.
> After I added "DEBUG=1" to "Preprocessor Macros", ran the helloCordova 
> target, DLog can be outputted.
> So here is my question:
> Should we add "DEBUG=1" to iOS template project->"Build Settings"-> 
> "Preprocessor Macros" ->"Debug" ?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to