Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Static libraries generate a framework podspec #53

Open
ilyapuchka opened this issue Nov 30, 2014 · 13 comments
Open

Static libraries generate a framework podspec #53

ilyapuchka opened this issue Nov 30, 2014 · 13 comments
Labels

Comments

@ilyapuchka
Copy link

When building with --library flag I got only *.a and no header files. Also podspec looks just like when building framework

@neonichu
Copy link
Member

neonichu commented 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.

@neonichu neonichu changed the title Static libraries are built without header files and with wrong podspec Static libraries are built with framework podspec Dec 1, 2014
@neonichu neonichu changed the title Static libraries are built with framework podspec Static libraries generate a framework podspec Dec 1, 2014
@neonichu neonichu added the bug label Dec 1, 2014
@ilyapuchka
Copy link
Author

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.

@neonichu neonichu added this to the Release 2.0 milestone Dec 15, 2014
@leviyehonatan
Copy link

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
Copy link
Member

The --library option isn't used very much. I'd love to accept a PR for this, though.

@ghost
Copy link

ghost commented 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
Copy link
Member

Nope, cp-packager hasn't been updated for 0.38.x, yet, see #90

@neonichu neonichu removed this from the Release 2.0 milestone Oct 7, 2015
@leviyehonatan
Copy link

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
Copy link
Member

The option works, but the generated podspec is incorrect.

@leviyehonatan
Copy link

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
Copy link

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 too

@mizhdi
Copy link

mizhdi commented Jul 26, 2017

mark

@panmingyang2009
Copy link

Today I also come across this issue.
I use the --library, and It just leave me a *.a and a wrong *.podspec without header file. I think it should give me header file too.

@leviyehonatan
Copy link

leviyehonatan commented Feb 8, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants