Date
1 - 3 of 3
Compiling and packaging libraries
majid.nasiry65@...
Hi
I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error.
I know default method for install libraries is versioned mode and I need to make symbolic links, but I don't know how?
Another question is what is difference between -dev and -dbg output?
I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error.
I know default method for install libraries is versioned mode and I need to make symbolic links, but I don't know how?
Another question is what is difference between -dev and -dbg output?
On 9/6/20 1:53 AM, majid.nasiry65@... wrote:
dbg packages contain debug info, which is useful if you are debugging on target.
[1] http://www.microhowto.info/howto/build_a_shared_library_using_gcc.html
Hiin library's build system you want to use symbol versioning during linker stage. Then you can create using ln cmd to creating symlink to lib.so and lib.so.<major_version> see [1]
I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error.
I know default method for install libraries is versioned mode and I need to make symbolic links, but I don't know how?
Another question is what is difference between -dev and -dbg output?dev packages contain, development headers and libraries which are useful for building packages on target
dbg packages contain debug info, which is useful if you are debugging on target.
[1] http://www.microhowto.info/howto/build_a_shared_library_using_gcc.html
Mike Looijmans
The simplest solution is to use autotools or Cmake for your project. That will automatically "do the right thing" to get the library properly installed and registered.
Even if your project is just one C file and a header, putting that in autotools or cmake is less work than getting all the nitty bits in a hand-crafted Makefile right.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijmans@...
W: www.topicproducts.com
Please consider the environment before printing this e-mail
toggle quoted message
Show quoted text
Even if your project is just one C file and a header, putting that in autotools or cmake is less work than getting all the nitty bits in a hand-crafted Makefile right.
Met vriendelijke groet / kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products B.V.
Materiaalweg 4, 5681 RJ Best
The Netherlands
T: +31 (0) 499 33 69 69
E: mike.looijmans@...
W: www.topicproducts.com
Please consider the environment before printing this e-mail
On 06-09-2020 10:53, majid.nasiry65 via lists.yoctoproject.org wrote:
Hi
I wrote a recipe for adding a library to my image it compile correctly but I have issues in installing it and I got "-dev package contains non-symlink .so" error.
I know default method for install libraries is versioned mode and I need to make symbolic links, but I don't know how?
Another question is what is difference between -dev and -dbg output?