0

I have a yocto build setup for a NXP dev-board. I can build images just fine and I thought this would be a simple way to cross compile a static library that I need for another project.

I added a recipe for the package, sqlcipher, and added sqlcipher-staticdev to IMAGE_INSTALL in local.conf.

This leads to me building sqlcipher just fine but I'm only getting dynamic libraries. I want to have a static library but even though I set DISABLE_STATIC = "" in the recipe I get nothing.

It has not been as easy as I first thought but is there a way to do this kind of thing? Is there something else that needs to be done to build a static lib?

evading
  • 3,032
  • 6
  • 37
  • 57
  • Are you sure you've rebuilt this package and rootfs? Try bitbake sqlcipher-staticdev -c cleanall, bitbake -C rootfs – pmod Dec 27 '16 at 21:29

1 Answers1

0

DISABLE_STATIC is appended to EXTRA_OECONF. Please check whether sqlcipher uses autotools to configure and whether has '--enable/disable-static' configure option.

Kai
  • 356
  • 1
  • 6
  • I have manually added --enable-static=yes to EXTRA_OECONF. Could that be overridden by autotools class? – evading Dec 22 '16 at 10:16
  • You could run `bitbake -e sqlcipher` to check the value of EXTRA_OECONF. What I mean is to check source code of sqlcipher to make sure it uses autotools and accept configure option '--enable-static'. If it uses other configure/build tools such as cmake, you need to figure out what controls static library build. – Kai Dec 27 '16 at 06:39
  • You could run 'bitbake -e sqlcipher' to check the value of EXTRA_OECONF. What I mean is to check source code of sqlcipher to make sure it uses autotools and accept configure option '--enable-static'. If it uses other configure/build tools such as cmake, you need to figure out what controls static library build. – Kai Dec 27 '16 at 06:40