- Add /usr/local/{bin,sbin} as last to find genbrk,
genccode and gencmn.
- Add more directories to qt_libdir and qt_incdir
- Make sure find libqt-mt.so and libDCOP.so with
a library major and minor in the filename where
the .so does not exists, but foo.so.0.0 does.
It's not good to use option descriptions like --enable/disable-*.
Also: If we want to replace default option descriptions with our owns,
then we shall describe them both (dependency-tracking).
Renamed all extensions to --enable-ext-* because
"we do want to present them together in ./configure --help"
See: b765a28ea9d63b60a14786b1a5484227175d413e
Deprecated old options not removed but commented instead.
¡There are still extensions which are only in build/configure.in!
Changed BUILD_TYPE from OOo to LibO
See: Elide all "SO:" and "OOo:" build.lst prefixes
- Pulled together all extension related options in one place in the
configure, they were cluttered all around the place. We do want to
present extensions together in ./configure --help.
- Add an -ext- to these configure options to clarify they are
extensions:
--enable-ext-presenter-ui, enable-ext-presenter-minimizer,
--enable-ext-presenter-console, enable-ext-pdfimport,
--enable-ext-wiki-publisher
(Similar changes should still be done to the rest of the extensions)
- Quit with explicit error message when using conflicting --without-java
and --enable-ext-wiki-publisher.
- Remove some minor things.
Signed-off-by: Sebastian Spaeth <Sebastian@SSpaeth.de>
Partially revert 58f59291db32e07b06311337be1e9f7a930291b2 - the name
here needs to match all those */prj/build.lst prefixes (which still
have "OOo:" at several places)
Use correct terminology for the Microsoft compilers, ".NET" was a part
of their name only in the 2003 version. Drop support for the 2003 and
2005 versions. The Platform SDK has been called the Windows SDK for
quite a while. Etc.
It isn't a Cygwin program anyhow, and isn't run from Cygwin, so no
need to check if it is "executable", or to chmod it "executable" from
a Cygwin point of view. No Windows file protection information will
propagate through the installer anyway, whatever the Cygwin chmod
would do.