Skip to content

Static libraries generate a framework podspec #53

Open
@ilyapuchka

Description

@ilyapuchka

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

Activity

neonichu

neonichu commented on Dec 1, 2014

@neonichu
Member

The omission of header files is intentional, as per the request to only build a library. The podspec is indeed wrong, though.

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
changed the title [-]Static libraries are built with framework podspec[/-] [+]Static libraries generate a framework podspec[/+] on Dec 1, 2014
ilyapuchka

ilyapuchka commented on Dec 3, 2014

@ilyapuchka
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.

added this to the Release 2.0 milestone on Dec 15, 2014
leviyehonatan

leviyehonatan commented on Apr 16, 2015

@leviyehonatan

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

neonichu commented on Apr 16, 2015

@neonichu
Member

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

ghost

ghost commented on Jul 28, 2015

@ghost

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

neonichu commented on Jul 28, 2015

@neonichu
Member

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

removed this from the Release 2.0 milestone on Oct 7, 2015
leviyehonatan

leviyehonatan commented on Feb 21, 2016

@leviyehonatan

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

neonichu commented on Feb 21, 2016

@neonichu
Member

The option works, but the generated podspec is incorrect.

leviyehonatan

leviyehonatan commented on Feb 22, 2016

@leviyehonatan

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

allentofight commented on May 28, 2016

@allentofight

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

3 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @neonichu@allentofight@ilyapuchka@leviyehonatan@mizhdi

        Issue actions

          Static libraries generate a framework podspec · Issue #53 · CocoaPods/cocoapods-packager