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

Shazron Abdullah commented on CB-3431:
--------------------------------------

For example, if you do a:
{code}
lipo -info libTestFlight.a
{code}

you get 3 archs:
{code}
Architectures in the fat file: libTestFlight.a are: armv7 (cputype (12) 
cpusubtype (11)) armv6 i386
{code}
                
> plugman - source-file framework=true - Build Error - can't find library 
> during Linker phase
> -------------------------------------------------------------------------------------------
>
>                 Key: CB-3431
>                 URL: https://issues.apache.org/jira/browse/CB-3431
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Plugman
>         Environment: plugman 0.7.6
> Cordova master/2.8.0
>            Reporter: Shazron Abdullah
>            Assignee: Filip Maj
>         Attachments: LIBRARY_SEARCH_PATHS.png, PBXPROJ.png, Screen Shot 
> 2013-05-21 at 11.26.54 AM.png
>
>
> This is separate from CB-3429 (which is fixed), and is apparent when you 
> actually try to build the project.
> Plugin tested with: https://github.com/shazron/TestFlightPlugin using plugman 
> 0.7.6
> The plugin installs fine, but when building, there is a linker error "library 
> TestFlight not found -lTestFlight".
> When manually adding a library to the Link Binary With Libraries section, 
> there is an additional step that Xcode automatically adds to your project, 
> namely adding the path of the library to the "Library Search Paths" of the 
> project's build settings. See "LIBRARY_SEARCH_PATHS.png" attached.
> Attached also is PBXPROJ.png where it shows how the setting looks like in the 
> Debug and Release configurations.
> Basically the fix is to add to the LIBRARY_SEARCH_PATHS build setting, and 
> add the path of the .a itself, but substitute $(SRCROOT) for the path of the 
> project.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to