How to relocate the example project?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system, documentation
Research direction
Start with the linked no_install_quickstart documentation, then compare its relocation instructions with the current boost-build.jam and Jamroot files and the shown Jamfile. Reproduce the move to a new project folder and investigate the reported unknown run-test rule. Done means the documentation matches the current files and gives a working relocation procedure.
Written by the indexing model from the issue text.
Description
Hello!
I've managed to build the example project but needed to relocate it to my project's folder. The documentation doesn't really reflect the current state of the code and I'm a bit lost when updating the jamfile to match this new folder.
Reading the currently available documentation it suggests changing some lines in the jamfile that point to the boost source folder, however as of boost 1.82.0 these lines don't exist in the jamfile anymore. In the docs we have
change the first path in boost-build.jam from
../../../../tools/build/src
to
/home/dave/boost_1_34_0/tools/build/srcand change the first path in Jamroot from
../../../..
to
/home/dave/boost_1_34_0
however the current jamfile looks like this
import python ;
project tutorial
: requirements
<location>.
;
python-extension hello_ext : hello.cpp ;
run-test hello : hello_ext hello.py ;
alias test : hello ;
explicit test ;
which results in an error when building,
ERROR: rule "run-test" unknown in module "Jamfile</home/userfolder/projectfolder>"
which I imagine stems from this misconfiguration as it builds fine in the original folder. I am not familiar enough with the jam build system and would appreciate some directions here.
Thanks in advance!
- 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