You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changed the title [-]Static libraries are built without header files and with wrong podspec[/-][+]Static libraries are built with framework podspec[/+]on Dec 1, 2014
Than I think podspec for library should definitely respect public header files section from original podspec. And I still think that headers should be copied to destination folder where library is created to make it easier and ready to use.
i am still surprised it is not implemented, whats the status of this? is this meant to be used as a fat static file generator for easing their creation?
Does "--library option isn't used very much" imply "so it's not supported at all"? I just ran --library and didn't get any file output. Should I expect a .a file somewhere?
Activity
neonichu commentedon Dec 1, 2014
The omission of header files is intentional, as per the request to only build a library. The podspec is indeed wrong, though.
[-]Static libraries are built without header files and with wrong podspec[/-][+]Static libraries are built with framework podspec[/+][-]Static libraries are built with framework podspec[/-][+]Static libraries generate a framework podspec[/+]ilyapuchka commentedon Dec 3, 2014
Than I think podspec for library should definitely respect public header files section from original podspec. And I still think that headers should be copied to destination folder where library is created to make it easier and ready to use.
leviyehonatan commentedon Apr 16, 2015
i am still surprised it is not implemented, whats the status of this? is this meant to be used as a fat static file generator for easing their creation?
neonichu commentedon Apr 16, 2015
The
--library
option isn't used very much. I'd love to accept a PR for this, though.ghost commentedon Jul 28, 2015
Does "--library option isn't used very much" imply "so it's not supported at all"? I just ran --library and didn't get any file output. Should I expect a .a file somewhere?
neonichu commentedon Jul 28, 2015
Nope, cp-packager hasn't been updated for 0.38.x, yet, see #90
leviyehonatan commentedon Feb 21, 2016
sorry to interrupt or anything, but what is the status of this, i am puzzled, can --library work with current released version of packager?
neonichu commentedon Feb 21, 2016
The option works, but the generated podspec is incorrect.
leviyehonatan commentedon Feb 22, 2016
as long as the library .a binary file is ok thats ok but last time we talked about this you said it won't work with latest cp
allentofight commentedon May 28, 2016
Today I also come across this issue,I use the
--library
, and It just leave me the *.a without header file,I think it should give me header file too3 remaining items