Skip to content

3rd party static libraries: Integrate Static Frameworks with the CLI Plugins Mechanism #147

@PanayotCankov

Description

@PanayotCankov

Subtask of #62

It only seems convenient to ask the users wrap static libraries that go with headers in a framework.

For example in case you have the libMyLibrary.a and a few headers that go with it (like the MagTek library) you can wrap it as:

MyLibrary.framework
├── MyLibrary <- libMyLibrary.a with the "lib" prefix and ".a" extension stripped
└── Headers
    ├── MyLibrary.h <- An umbrella header that eventually includes ClassA.h and ClassB.h
    ├── ClassA.h
    └── ClassB.h

In any case it seems more convenient to use this convention rather than inventing a home made package.json configuration.

So packed frameworks will be usable in nativescript.

Metadata

Metadata

Assignees

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions