try the -r flag which is for prelinking. you can see that in the .mk file
And of course a debug version contains tons of symbols in order for the
debugger to be able to do its work.
iOS has allowed dylibs since iOS 8 and the introduction of Swift. In fact
you can't produce a static lib with Swift, only a dylib.
For our Pdfium wrapper we produce a static lib out of the Pdfium code
itself, and link that in a framework project with the swift wrappers, to
produce a dylib which is a swift module that can be imported into an app.
Beside the linking benefits this then gives you a nice encapsulated library
that is easy to consume from swift.
that was my first attempt but the apple developers said no, will try to
scan through the doc again.
If I have time over the next couple of days I'll have a go at creating a
framework to see if it does actually behave as I expect.
or a lot easier simply change the .mk to build a .dylib instead of the .a
thr .o file within both should be identical.
rgds
jan i
--
Sent from My iPad, sorry for any misspellings.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.