Re: [boost] [boostorg/python] Building against multiple python implementations broken on 1.70 (#262)
On 2019-04-14 7:50 p.m., Peter Dimov wrote:
I'll need to look into this. Apparently, |FindBoost.cmake| solves this by forcing the user to specify the version in |find_package(Boost COMPONENTS python27)|, but the CMake configuration files installed by 1.70 only take |find_package(Boost COMPONENTS python)|, so multiple versions installed at the same time are a problem.
In the meantime, you can add |--no-cmake-config| to your |b2 install| command line to skip the installation of CMake configuration files, which ought to give you the 1.69 behavior back.
This is *exactly* the kind of situation I was afraid of when I argued strongly against adding CMake support to my own projects: Before I had to deal with B2 issues that I had difficulties resolving myself. Now I have to deal with B2 *and* CMake issues, being even more dependent on others. That's not my definition of progress. Stefan -- ...ich hab' noch einen Koffer in Berlin...
Stefan Seefeld wrote:
On 2019-04-14 7:50 p.m., Peter Dimov wrote:
I'll need to look into this. Apparently, |FindBoost.cmake| solves this by forcing the user to specify the version in |find_package(Boost COMPONENTS python27)|, but the CMake configuration files installed by 1.70 only take |find_package(Boost COMPONENTS python)|, so multiple versions installed at the same time are a problem.
In the meantime, you can add |--no-cmake-config| to your |b2 install| command line to skip the installation of CMake configuration files, which ought to give you the 1.69 behavior back.
This is *exactly* the kind of situation I was afraid of when I argued strongly against adding CMake support to my own projects: Before I had to deal with B2 issues that I had difficulties resolving myself. Now I have to deal with B2 *and* CMake issues, being even more dependent on others.
It's even worse than that. _I_ have to deal with them.
On 2019-04-14 8:39 p.m., Peter Dimov via Boost wrote:
Stefan Seefeld wrote:
On 2019-04-14 7:50 p.m., Peter Dimov wrote:
I'll need to look into this. Apparently, |FindBoost.cmake| solves
this > by forcing the user to specify the version in |find_package(Boost > COMPONENTS python27)|, but the CMake configuration files installed by > 1.70 only take |find_package(Boost COMPONENTS python)|, so multiple > versions installed at the same time are a problem.
In the meantime, you can add |--no-cmake-config| to your |b2
install| > command line to skip the installation of CMake configuration files, > which ought to give you the 1.69 behavior back.
This is *exactly* the kind of situation I was afraid of when I argued strongly against adding CMake support to my own projects: Before I had to deal with B2 issues that I had difficulties resolving myself. Now I have to deal with B2 *and* CMake issues, being even more dependent on others.
It's even worse than that. _I_ have to deal with them.
Right. So what's your suggestion / conclusion for to resolve this ? Stefan -- ...ich hab' noch einen Koffer in Berlin...
Stefan Seefeld wrote:
Right. So what's your suggestion / conclusion for to resolve this ?
I'm working on it. I could use a little help. What is the correct way to configure Boost.Build's `python` on Travis Xenial, which supposedly has Python 2.7.15, 3.6.7, and 3.7.1 preinstalled? https://docs.travis-ci.com/user/reference/xenial/#python-support I tried putting using python : 2.7 ; using python : 3.6 ; using python : 3.7 ; in ~/user-config.jam, but that doesn't seem to work. With `python=2.7,3.6,3.7` I get /home/travis/build/boostorg/boost-root/tools/build/src/build/feature.jam:491: in feature.validate-value-string from module feature error: "3.6" is not a known value of feature <python> error: legal values: "2.7" /home/travis/build/boostorg/boost-root/tools/build/src/build/property.jam:345: in validate1 from module property /home/travis/build/boostorg/boost-root/tools/build/src/build/property.jam:371: in property.validate from module property /home/travis/build/boostorg/boost-root/tools/build/src/build/build-request.jam:271: in convert-command-line-element from module build-request /home/travis/build/boostorg/boost-root/tools/build/src/build/build-request.jam:222: in build-request.convert-command-line-elements from module build-request /home/travis/build/boostorg/boost-root/tools/build/src/build-system.jam:774: in load from module build-system /home/travis/build/boostorg/boost-root/tools/build/src/kernel/modules.jam:295: in import from module modules /home/travis/build/boostorg/boost-root/tools/build/src/kernel/bootstrap.jam:139: in boost-build from module /home/travis/build/boostorg/boost-root/boost-build.jam:17: in module scope from module
On 2019-04-15 4:37 p.m., Peter Dimov via Boost wrote:
Stefan Seefeld wrote:
Right. So what's your suggestion / conclusion for to resolve this ?
I'm working on it. I could use a little help.
Sorry, my understanding of all that is very limited. I suspect Rene and Steven will be best equipped to help with those questions.
What is the correct way to configure Boost.Build's `python` on Travis Xenial, which supposedly has Python 2.7.15, 3.6.7, and 3.7.1 preinstalled?
https://docs.travis-ci.com/user/reference/xenial/#python-support
I tried putting
using python : 2.7 ; using python : 3.6 ; using python : 3.7 ;
in ~/user-config.jam, but that doesn't seem to work. With `python=2.7,3.6,3.7` I get
/home/travis/build/boostorg/boost-root/tools/build/src/build/feature.jam:491: in feature.validate-value-string from module feature error: "3.6" is not a known value of feature <python> error: legal values: "2.7" /home/travis/build/boostorg/boost-root/tools/build/src/build/property.jam:345: in validate1 from module property /home/travis/build/boostorg/boost-root/tools/build/src/build/property.jam:371: in property.validate from module property /home/travis/build/boostorg/boost-root/tools/build/src/build/build-request.jam:271: in convert-command-line-element from module build-request /home/travis/build/boostorg/boost-root/tools/build/src/build/build-request.jam:222: in build-request.convert-command-line-elements from module build-request /home/travis/build/boostorg/boost-root/tools/build/src/build-system.jam:774: in load from module build-system /home/travis/build/boostorg/boost-root/tools/build/src/kernel/modules.jam:295: in import from module modules /home/travis/build/boostorg/boost-root/tools/build/src/kernel/bootstrap.jam:139: in boost-build from module /home/travis/build/boostorg/boost-root/boost-build.jam:17: in module scope from module
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Stefan -- ...ich hab' noch einen Koffer in Berlin...
participants (3)
-
Peter Dimov -
stefan -
Stefan Seefeld