meta-openembedded/meta-oe
Gyorgy Sarvari 91a0e89229
jsonrpc: fix interface library paths in cmake files
The cmake files generated by this recipe contain a number
of interfacing libraries, with absolute paths, which also
contain the TMPDIR. The TMPDIR part of these paths were
just truncated by the recipe, to avoid the corresponding
QA check error.

However this made it impossible to to link against this
library from other recipes. When one tried, the find_package
command failed with the following error:

| Run Build Command(s): ninja -v -j 12 all
| ninja: error: '/usr/lib/libjsoncpp.so', needed by 'jsonrpctest', missing and no known rule to make it

To avoid this, instead of just truncating this path, set it to
${CMAKE_SYSROOT} placeholder (which is resolved by CMake to
the correct value at build-time, using the variable set by
cmake.bbclass)

Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-02-13 20:54:51 -08:00
..
classes capnproto: remove binaries from target-build, add bbclass 2025-02-03 11:25:22 -08:00
conf spdm-utils: Initial support for spdm-utils 2025-02-04 20:25:51 -08:00
dynamic-layers android-tools: build without gold 2025-02-12 09:16:08 -08:00
files influxdb: Add missing group to static id 2024-02-17 17:35:24 -08:00
lib/oeqa/selftest/cases
licenses openldap: make license match spdx identifier 2025-02-04 20:25:51 -08:00
recipes-benchmark recipes: Fix variable assignment whitespace 2025-01-31 10:34:03 -08:00
recipes-bsp nvme-cli: Fix musl build erros for v2.11 2024-11-21 21:42:36 -08:00
recipes-connectivity zabbix: upgrade 6.2.7 -> 6.4.21 2025-02-12 23:45:35 -08:00
recipes-core plymouth: remove extra kernel parameter 2025-01-30 12:30:08 -08:00
recipes-crypto botan: upgrade 3.6.1 -> 3.7.1 2025-02-10 08:45:35 -08:00
recipes-dbs mariadb: correct STACK_DIRECTION setting 2025-02-13 07:44:16 -08:00
recipes-devtools jsonrpc: fix interface library paths in cmake files 2025-02-13 20:54:51 -08:00
recipes-extended can-utils: Split mcp251fd* into sub-package 2025-02-13 07:44:16 -08:00
recipes-gnome libjcat: upgrade 0.2.2 -> 0.2.3 2025-02-10 08:45:36 -08:00
recipes-graphics ttf-takao: update SRC_URI 2025-02-12 23:45:35 -08:00
recipes-kernel crash-cross-canadian: Update to match OE-Core virtual provider changes 2025-01-25 09:36:49 -08:00
recipes-multimedia audiofile: mark CVE-2020-18781 as patched 2025-01-17 16:39:40 -08:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-09-27 06:18:13 -07:00
recipes-networking/cyrus-sasl Drop unnecessary SRC_URI md5sum from the recipes in meta-oe. 2024-11-05 19:19:22 -08:00
recipes-printing cups-filters: include UPSTREAM_CHECK_URI to fix UNKNOWN_BROKEN status 2024-07-24 08:56:30 -07:00
recipes-security nmap: fix racing issue at do_compile 2025-02-12 09:16:07 -08:00
recipes-shells dash: set CVE_PRODUCT 2024-12-10 13:43:54 -08:00
recipes-support libspdm: add support for ppc64le 2025-02-12 14:12:42 -08:00
recipes-test syzkaller: network in compile is not needed 2024-12-10 08:39:04 -08:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -07:00
SECURITY.md meta: Add SECURITY.md file to all layers 2024-11-23 09:00:14 -08:00

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj raj.khem@gmail.com