![]() ![]() The claim is that it is useful for libraries to provide users the option of using a library as a ‘header only’ library and adding preprocessor magic to make that possible. Recently there was a blog post describing an example library which can be built as a shared library, or as a static library, or used directly as a ‘header only’ library which doesn’t require the user to link against anything to use the library. There are also many other examples of such ‘header only’ libraries. Boost is a widespread source of many ‘header only’ libraries, which don’t require a user to link to a particular platform-compatible library binary. There is a category of libraries which considers the portable binaries issue to be a terminal one. Libraries like Qt distribute dynamically compiled binaries for major platforms and other libraries have comparable solutions. ![]() Linking works differently, compilers bundle different code into binaries on each platform etc. Library binaries compiled on Windows/OSX/Linux can not simply be copied over to another platform and used there. Library file under usr/include and usr/lib respectively.Using a C++ library, particularly a 3rd party one, can be complicated affair. Yes the simple1-dev directory contains the include files and the areĪny of the directories under packages-split within the workdir forĪt the moment it looks like it isn't producing anything. So is your recipe actually producing any packages at all? i.e. * opkg_install_cmd: Cannot install package simple1-staticdev.įor reference here is my simple1 recipe, maybe I'm missing TOOLCHAIN_HOST_TASK_append = " simple1-staticdev"Īgain if I try adding this to my image recipe I get a similar error If you want a single staticdev package in the SDK you'd need to add the SDKIMAGE_FEATURES = "dev-pkgs dbg-pkgs staticdev-pkgs" In your image, add the following to your nf (or the TOOLCHAIN_TARGET_TASK_append = " simple1-staticdev" TOOLCHAIN_TARGET_TASK rather than TOOLCHAIN_HOST_TASK i.e.: To this as there really isn't much of any documentation on how the cmakeĪctually I realised I made a mistake above that might explain why the second If my understanding is wrong then that's totally understandable as I'm new usr/lib/*.o /usr/lib/pkgconfig /usr/share/pkgconfig /usr/share/aclocal Assuming, your FILES_$/*.la"įILES_jsoncpp-dev="/usr/include /lib/lib*.so /usr/lib/lib*.so /usr/lib/*.la You need to explicitly RDEPENDS your-unit-staticdev and your-unit in your image's packagegroup. On Sep 22, 2014, at 7:52 PM, Joseph Andrew de la Peña > wrote: I tried adding simple1-staticdev to IMAGE_INSTALL and I get an error that it doesn't exist. ![]() Where does this stuff go? In a Packagegroup file. Thanks for the response but I'm not sure that I understand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |