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

ASF GitHub Bot commented on CB-9517:
------------------------------------

GitHub user tripodsan opened a pull request:

    https://github.com/apache/cordova-lib/pull/281

    CB-9517 Adding a plugin on iOS/OSX that uses a private framework does…

    see also related PR https://github.com/apache/cordova-osx/pull/14
    
    todo:
    * update the project templates for osx / ios if desired or create the 
copy-files build phase automatically
    * talk to the guys from node-xcode if we should add this to their code

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tripodsan/cordova-lib CB-9517

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cordova-lib/pull/281.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #281
    
----
commit 6110b7656f0975f7ac0865d4241670baeb7860f2
Author: Tobias Bocanegra <[email protected]>
Date:   2015-08-19T21:29:13Z

    CB-9517 Adding a plugin on iOS/OSX that uses a private framework does not 
work

----


> Adding a plugin on OSX that uses a private framework does not work
> ------------------------------------------------------------------
>
>                 Key: CB-9517
>                 URL: https://issues.apache.org/jira/browse/CB-9517
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: OSX
>    Affects Versions: 3.5.0
>            Reporter: Tobias Bocanegra
>            Assignee: Tobias Bocanegra
>
> problems so far:
> - no copy-files step added for embedded framework
> - the {{LD_RUNPATH_SEARCH_PATHS}} is not correctly set



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to