Open travisariggs opened 1 year ago
I haven't tried it on x86_64, only aarch64. Hmm. You might start with adding this to the depthai-core recipe:
EXTRA_OECMAKE += " -DCMAKE_POSITION_INDEPENDENT_CODE=ON"
edit: actually if PACKAGECONFIG contains shared it should be okay. Are you overriding PACKAGECONFIG for the recipe?
Also be sure you're aware of this one: https://github.com/jwinarske/meta-luxonis/issues/3 If it's enabled it will clean up things needed to link. I haven't solved this just yet
I looked over Issue #3 before I logged this one. I did not have rm_work
in my local conf. (I was able to reproduce that issue when I added rm_work
to my local conf, but that is not my issue.)
According to bb -e depthai-core
, I found:
PACKAGECONFIG="shared examples tests opencv resource-compile"
So, it looks like it contains "shared" as you suggested.
Grepping through your layer, it looks like this line turns on position-independent code if PACKAGECONFIG
contains "shared":
${@bb.utils.contains('PACKAGECONFIG', 'shared', '-DCMAKE_POSITION_INDEPENDENT_CODE=ON', '-DCMAKE_POSITION_INDEPENDENT_CODE=OFF', d)}
During all of my attempts so far, I have been building from the tip of your kirkstone branch (2394f5a
). I haven't modified your recipe yet. So, I don't think I have attempted to override PACKAGECONFIG
in any way.
Just for kicks, I tried adding your suggested line to depthai-core_2.20.2.bb
at line 150, just after the block of EXTRA_OECMAKE
.
It failed the same way.
I think I've fixed it.
I added -D CMAKE_POSITION_INDEPENDENT_CODE=ON
to the EXTRA_OECMAKE
arguments in the libarchive-luxonis_git.bb
recipe.
That built successfully on my machine, although I did get a QA warning...not sure how important it is.
WARNING: depthai-core-2.20.2-r0 do_package_qa: QA Issue: depthai-core-dbg: found library in wrong location: /usr/bin/luxonis/examples/.debug/libutility.so
depthai-core-examples: found library in wrong location: /usr/bin/luxonis/examples/libutility.so [libdir]
I sent you a PR for the kirkstone branch. I am curious if this still works for your system.
First, Joel, thank you for publishing this layer.
I am trying to build
depthai-core
on the kirkstone branch with bitbake, but getting a failure.Full disclosure: I am not a Yocto expert.
Here are some of the key lines of the log surrounding the failure:
Full log attached here: log.do_compile.820910.log
Here is the output of
bb -e depthai-core
: yocto-e.logDo you have any suggestions?