ChimeraTK / ChimeraTK/cppext

yocto: Adds reference to local build sysroot into .cmake file

Open
#21 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2
Forks
2
Avg merge
1m
Merged PRs (30d)
1

Description

bitbake sets up a local compilation sysroot for its packages. We then hardcode the path to libatomic into our .cmake.

If that package is moved into the shared state of the build and later used to build another package, the private sysroot reference is imported into the build of the dependency, and the library is no longer found because the original mini-sysroot was already removed

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the .cmake file that hardcodes the libatomic path and trace how BitBake creates and exports the local compilation sysroot. Reproduce the shared-state reuse scenario and verify that a dependent package can still find libatomic after the original mini-sysroot is removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, cpp
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.