Confusion about using Faber to Build
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- build-system
Research direction
Start by reproducing faber test.report on Ubuntu 20.04 and inspect the generated src/g++-9/x86_64/shared/libboost_python37.so path. Check the repository's Faber build targets and existing usage guidance for an install step or CMake-compatible location. Done means documenting the required command and how another CMake project can find the built library.
Written by the indexing model from the issue text.
Description
Hi,
I'm trying to build the library (Ubuntu 20.04, Python 3.7 installed from Deadsnakes, Boost installed from Aptitude). When I clone the repo and run Faber, the build seems to succeed.
When I run faber test.report, most of the tests pass. I get the following
test summary: 85 passes, 4 expected failures, 3 skipped
But, when I try to link against this from my other project--a project that uses the typical CMake search function--it can't find the library. Is there some install command I need to run in order to put the binary in the right place? Something similar to make install? I see the binary inside the repo at src/g++-9/x86_64/shared/libboost_python37.so
Thanks!
- Dominant language
- C++
- Stars
- 537
- Forks
- 223
- Avg merge
- 11h 22m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/python
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
BoostDetectToolset-1.90.0.cmake file not found in an include() call in boost_python-config.cmake Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100