Opened 10 years ago

Closed 8 years ago

#73 closed defect (fixed)

make sure third party projects can be disabled

Reported by: andreasw Owned by: andreasw
Priority: minor Component: configuration tests
Version: 0.5 Keywords:
Cc:

Description

For some of the third party projects, it does not work to specify --without-blabla to make sure that they are not compiled even when their source code is there.

  • metis: --without-metis crashes configure script
  • lapack: --without-lapack still compiles LAPACK code if it is there, but it is not linked into executable
  • mumps: --without-mumpslib ?
  • ASL: --without-asldir still compiles ASL, but does not link it into the code (e.g., Ipopt)

Change History (2)

comment:1 Changed 10 years ago by stefan

Setting COIN_SKIP_PROJECT to the corresponding ThirdParty/XXX directory seems to work. At least that's what we do for the binary distribution builds.

Stefan

comment:2 Changed 8 years ago by stefan

  • Resolution set to fixed
  • Status changed from new to closed

For any project xxx, specifying --without-xxx-lib, --without-xxx-incdir, or --without-xxx-datadir should lead to disabling xxx. For Blas and Lapack, also --without-blas and --without-lapack are available.

In the base directory, it leads to not configuring xxx and not checking for an installed version of the project (as if it were specified in COIN_SKIP_PROJECT). In the project directory, it leads to not searching for xxx (as if it were specified in COIN_SKIP_PROJECT).

This is in BuildTools/trunk and BuildTools/stable/0.7 and should thus be in the next releases of projects that use BuildTools 0.7.

Note: See TracTickets for help on using tickets.