[Olena] --with vs. --enable

Je crois que --with et --enable ne sont pas compris : Vaucanson et Olena tous deux doivent revoir leur configure.ac. --with : option sur un paquetage externe --enable : option interne du paquetage. Vcn: Optional Features: --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --disable-dependency-tracking speeds up one-time build --enable-dependency-tracking do not reject slow dependency extractors --enable-shared[=PKGS] build shared libraries [default=yes] --enable-fast-install[=PKGS] optimize for fast installation [default=yes] --disable-libtool-lock avoid locking (might break parallel builds) --enable-xml Enable XML tests (need Xerces-C++ library >= 2.3) Optional Packages: --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) ** --with-vcsn=DIR Include directory where Vaucanson is installed ** (optional) ** --without-vaucanswig disable building vaucanswig --with-pic try to use only PIC/non-PIC objects [default=use both] --with-gnu-ld assume the C compiler uses GNU ld [default=no] --with-xerces specify Xerces-C++ location Oln: Optional Features: --disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no) --enable-FEATURE[=ARG] include FEATURE [ARG=yes] --disable-dependency-tracking speeds up one-time build --enable-dependency-tracking do not reject slow dependency extractors --disable-manpages-regen force disable regeneration of manual pages Optional Packages: --with-PACKAGE[=ARG] use PACKAGE [ARG=yes] --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) ** --with-oln=DIR Include directory where Olena is installed (optional) --with-zlib[=DIR] using zlib (DIR = prefix for zlib installation) --with-fftw[=DIR] using fftw (DIR = prefix for fftw installation) ** --without-oln-testsuite disable building the olena's testsuite ** --with-oln-tests=<list> none,all,convert,convol,io,morpho,sanity,transforms ** --without-ntg-testsuite disable building the integre's testsuite ** --with-ntg-tests=<list> none,types ** --without-mlc-testsuite disable building the metalic's testsuite ** --with-mlc-tests=<list> none,array,main Doxygen is needed to build the doc ** --without-doc disable building the documentation ** --without-doc-ref disable building the Olena reference manuals ** --without-doc-dev disable building the Olena development manual ** --without-demo disable building the demonstration programs ** --without-tools disable building the run-time tools ** --without-utilities disable building the command-line utilities ** --without-morpho-utilities ** disable building the morpho utilities ** --without-swilena disable building the SWIG interface to Olena ** --without-pylena disable building the Python interface to Olena ??? Include path for Python.h ** --without-rblena disable building the Ruby interface to Olena ??? Include path for ruby.h Par ailleurs les lignes en ??? sont très étranges. ------------------------------------------------------------ 12.1 Working With External Software =================================== Some packages require, or can optionally use, other software packages that are already installed. The user can give `configure' command line options to specify which such external software to use. The options have one of these forms: --with-PACKAGE[=ARG] --without-PACKAGE For example, `--with-gnu-ld' means work with the GNU linker instead of some other linker. `--with-x' means work with The X Window System. The user can give an argument by following the package name with `=' and the argument. Giving an argument of `no' is for packages that are used by default; it says to _not_ use the package. An argument that is neither `yes' nor `no' could include a name or number of a version of the other package, to specify more precisely which other package this program is supposed to work with. If no argument is given, it defaults to `yes'. `--without-PACKAGE' is equivalent to `--with-PACKAGE=no'. `configure' scripts do not complain about `--with-PACKAGE' options that they do not support. This behavior permits configuring a source tree containing multiple packages with a top-level `configure' script when the packages support different options, without spurious error messages about options that some of the packages support. An unfortunate side effect is that option spelling errors are not diagnosed. No better approach to this problem has been suggested so far. For each external software package that may be used, `configure.ac' should call `AC_ARG_WITH' to detect whether the `configure' user asked to use it. Whether each package is used or not by default, and which arguments are valid, is up to you. ---------------------------------------------------------------------- 12.2 Choosing Package Options ============================= If a software package has optional compile-time features, the user can give `configure' command line options to specify whether to compile them. The options have one of these forms: --enable-FEATURE[=ARG] --disable-FEATURE These options allow users to choose which optional features to build and install. `--enable-FEATURE' options should never make a feature behave differently or cause one feature to replace another. They should only cause parts of the program to be built rather than left out. The user can give an argument by following the feature name with `=' and the argument. Giving an argument of `no' requests that the feature _not_ be made available. A feature with an argument looks like `--enable-debug=stabs'. If no argument is given, it defaults to `yes'. `--disable-FEATURE' is equivalent to `--enable-FEATURE=no'. `configure' scripts do not complain about `--enable-FEATURE' options that they do not support. This behavior permits configuring a source tree containing multiple packages with a top-level `configure' script when the packages support different options, without spurious error messages about options that some of the packages support. An unfortunate side effect is that option spelling errors are not diagnosed. No better approach to this problem has been suggested so far. For each optional feature, `configure.ac' should call `AC_ARG_ENABLE' to detect whether the `configure' user asked to include it. Whether each feature is included or not by default, and which arguments are valid, is up to you. ---------------------------------------------------------------------- Merci aux groupes de s'aligner sur le std, et de ne pas oublier, le cas échéant, de mettre à jour README. Oln: Remarquer que cette remarque est liée à une task que j'ai mise dans votre groupe, et qui n'a tjs pas de réponse...