https://issues.apache.org/ooo/show_bug.cgi?id=118604
--- Comment #1 from Andre <[email protected]> 2011-11-16 12:49:25 UTC --- Created attachment 77025 --> https://issues.apache.org/ooo/attachment.cgi?id=77025 Added support for pre-installed dmake and for downloading source This is a first version of handling dmake. Using, downloading, and/or building of dmake works like this: 1. If no other (dmake) option is given, then configure tries to locate a pre-installed dmake executable in the usual (and system dependent) places. 2a. When it is not found and --with-dmake-path=<path-to-executable> is given to configure then the dmake executable is searched for in the specified path. This option is only necessary when dmake has been installed into a non-standard location, where it is not found by configure. 2b. When it is not found and --with-dmake-url=<url-to-source-package> is given to configure then the bootstrap script (by means of the fetch_tarballs.sh script) will download a source package from the given URL. This package is expected to have a top-level directory that is identical to the package name without the file extension. The package may be a .tar.gz/.tgz, .tar.bz2, or .zip archive. The package is unpacked and built and the resulting dmake.exe is deployed to the solver module. 3. (Temporary) If none of the above works, then the internally provided dmake source code in the dmake module is built and the resulting executable is deployed. -- Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
