>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I think that the more magic you perform, the more you increase
Angus> the likelihood of breaking something. Making these changes just
Angus> before a release is a bad idea IMO.
I am not planning to do that in 1.3.x, just pondering 1.4.0. I am
always interested to see what other people use as options.
Angus> In fact, I think that you should celebrate the fact that you've
Angus> achieved your *primary* goal already: the configure system has
Angus> enough knobs to allow LyX to be built on all systems *now*.
Angus> Moreover, these knobs are all documented and are usable by the
Angus> uninitiated.
Yes, but I'd like to reduce the number of knobs as much as possible.
>> So you mean that QT_DIR should be changed to be a precious
>> variable, right?
>>
>> -- Macro: AC_ARG_VAR (VARIABLE, DESCRIPTION) Declare VARIABLE is a
>> precious variable, and include its DESCRIPTION in the variable
>> section of `./configure --help'.
Angus> No, I mean that we have a --with-qt-dir arguement that is
Angus> understood by configure and that I use it. Note that QT_DIR is
Angus> not the same as QTDIR which the Qt build system treats as
Angus> "special".
Is there a reason why you use QT_DIR instead of QTDIR?
Angus> All I'm trying to do is tell the build system that it should
Angus> look for the Qt library/header files at
Angus> J:\MinSYS\home\Angus\qt3\{lib,include}
That's QTDIR.
In configure script if for example your CC variable has some value
when you run the script (even without passing CC=mycc on the command
line), this value will be remembered later. Users can reasonably
expect that this will be true with QTDIR too. So making this change
would make the configure script more predictable (and incidentally
remove a part of your command line).
Angus> The present system works; why are you interested in changing it
Angus> now? (Just before a release.)
I am not trying to change it now.
JMarc
