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

Comments

Projects
None yet
7 participants
@ilyapuchka
Copy link

commented Nov 30, 2014

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

@neonichu

This comment has been minimized.

Copy link
Member

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

This comment has been minimized.

Copy link
Author

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

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

@leviyehonatan

This comment has been minimized.

Copy link

commented 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

This comment has been minimized.

Copy link
Member

commented Apr 16, 2015

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

@ghost

This comment has been minimized.

Copy link

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

This comment has been minimized.

Copy link
Member

commented Jul 28, 2015

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

This comment has been minimized.

Copy link

commented 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

This comment has been minimized.

Copy link
Member

commented Feb 21, 2016

The option works, but the generated podspec is incorrect.

@leviyehonatan

This comment has been minimized.

Copy link

commented 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

This comment has been minimized.

Copy link

commented 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 too

@mizhdi

This comment has been minimized.

Copy link

commented Jul 26, 2017

mark

@panmingyang2009

This comment has been minimized.

Copy link

commented Feb 7, 2018

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

This comment has been minimized.

Copy link

commented Feb 8, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.