Edoardo Pasca

I haven't pip installed nipet, I've cloned the repo and started building as you suggest in the readme: ```bash # ... or build & install directly with cmake mkdir build...

So, ``` lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic ``` I ran ```bash sudo apt update sudo apt upgrade...

There must be more than this going on. On my old machine it still fails with the old message, even after upgrading to 10.1 from NVIDIA, rather than from [ubuntu](https://github.com/SyneRBI/SyneRBI_VM/blob/1642bd794de08fdbc185fc50f70e3e6c1ed41284/README.md#install-cuda-101).

Yes we are building it. For Unix is easy to remove the python module: https://github.com/CCPPETMR/SIRF-SuperBuild/blob/master/SuperBuild/External_Boost_configureboost.cmake#L26 For Windows I don't quite understand where do we set which boost modules to build.

All right, then for windows [isn't there](https://github.com/CCPPETMR/SIRF-SuperBuild/blob/master/SuperBuild/External_Boost_buildboost.cmake#L26) already.

I usually trip over this behaviour myself. I'd rather implement your solution 2, with the caveat that I would default to OFF and keep the default CMake behaviour.

That's a known problem. In the VM we specify those https://github.com/SyneRBI/SIRF-SuperBuild/blob/448356272bf150846115daeafe55a2e600c1a1cd/VirtualBox/scripts/UPDATE.sh#L145-L146 and use them as https://github.com/SyneRBI/SIRF-SuperBuild/blob/448356272bf150846115daeafe55a2e600c1a1cd/VirtualBox/scripts/UPDATE.sh#L191-L206

I think modern Ubuntu, later than 22.04, do not ship with python2 and this issue can be closed, @KrisThielemans ?

Isn't it that we use consistently `DISABLE_GIT_CHECKOUT_${proj}` for all the dependencies? I'd close this issue. https://github.com/SyneRBI/SIRF-SuperBuild/blob/ec4b9c50bb650101e232590405c06eaf417256a6/CMake/SetGitTagAndRepo.cmake#L37

The second option seems better to me.