The library that we use (node-xcode) supports: System Frameworks, Custom Frameworks (ones you would drag&drop into your project) and static libraries. It does not support XCode subprojects as far as I know. If you want to add support for it, you're more than welcome. Repository is right here: https://github.com/alunny/node-xcode
Anis On Fri, Sep 18, 2015 at 11:14 PM Tobias Bocanegra <tri...@apache.org> wrote: > Hi, > > I want to add a plugin to a ios/osx project. the plugin contains a > .xcodeproj of a static library, incuding the sources. I want to avoid > distributing the binary .a in the plugin. > > I tried various ways of how to specify this library, with <framework> > with <src framework=true> etc. but it never adds the lib.a to the > linker section in build phases. > > looking at the pbxproj, it looks like it would have to specify a proxy > reference to the library project. which is a bit more complex than > just add the framwork reference. > > Is this something that would be desired by others? If so, I can try to > improve the plugman script to deal property with the library. > > the 2nd problem is, that xcode usually has the sources beside the > xcodeproj. so for example: > > mylib.xcodeprj/ > mylib/ > > but there is no tag to copy an entire directory. using the <framework> > tag also for the sources, would embed it to the frameworks section, > which is also wrong. > > ideally we would be able to specify the source directory, like > > <framework src="frameworks/osx/mylib.xcodeproj" custom="true" > sources="frameworks/osx/mylib" /> > > OR > > add a new sub-project tag, like: > > <sub-project src="frameworks/osx/mylib" > project="frameworks/osx/mylib.xcodeproj" framework="true" > link-targets="libMyLib.a" /> > > WDYT? > > Regards, Toby > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
