Jean-Marc Lasgouttes wrote:
> Angus> Why is the "--prefix=C:/Program Files/LyX" argument unquoted,
> Angus> especially given that all others are quoted as expected?
> 
> This one comes from here (in configure):
> 
>   # Always prepend --prefix to ensure using the same prefix
>   # in subdir configurations.
>   ac_sub_configure_args="--prefix=$prefix $ac_sub_configure_args"

Achh. That's a bit of autogenerated stuff isn't it? Is it possible to 
first modify $prefix as something like:

        prefix_safe=$prefix
        prefix="'$prefix'"
        # invoke ac_sub_configure_args
        ...
        prefix=prefix_safe
        unset prefix_safe

> Angus> $ ../configure --prefix='J:/Program Files/LyX' ...
> 
> Angus> Hmmm. Interesting. Notice the extra --prefix arg passed to the
> Angus> reLyX configure script:
> 
> Same problem as above. But it is fixed by overquoting, right?

Well, no, not really. The reLyX configure script is being passed stuff 
that it is complaining about. It would be best if it didn't complain, no?

> Angus> 3. Using a wrapper script to invoke configure
> 
> Angus> The script.
> 
> Angus> #! /bin/sh cd build-qt ../configure --prefix='J:/Program\
> Angus> Files/LyX' \ --enable-maintainer-mode --with-version-suffix \
> Angus> --with-included-gettext --with-frontend=qt \
> Angus> --with-qt-dir=$QTDIR --with-qt-libraries=$QTDIR/lib \
> Angus> --with-qt-includes=$QTDIR/include
> 
> Why do you set --with-qt-libraries and --with-qt-includes? I would
> think --with-qt-dir is enough.

I'm not sure, actually.

On a Debian machine I need only the --with-qt-includes:
--with-qt-includes=/usr/include/qt3

On the Windows machine you're probably right that I need only 
--with-qt-dir.

> Angus> Installation fails:
> [in mkinstalldirs]
> 
> It seems that the mkinstalldirs we use in 1.4.0cvs has special code to
> handle spaces and use mkdir -p if possible. Could you try with to put
> it in 1.3.x/config/ and see whether it helps?

I'll try.

I take it that you'd like all this stuff to work perfectly on both *nix 
and on Windows before I commit it to the 1.3.x tree?

Things to do post patch:
1. PATHs. There's stuff hard-coded to set the PATH on a Mac to include a 
bunch of directories including that of the LyX executable so that reLyX et 
al are found. Some such similar thing is needed on Windows, so I'd guess 
that a LyXRC variable is the best solution here.

2. LyX currently doesn't behave too well if the root temp directory does 
not exist. I guess that it should try to create it and exit if it fails.

-- 
Angus

Reply via email to