Jean-Marc Lasgouttes wrote:
> Angus> To recap, on Windows we attempt to execute the lib/configure
> Angus> script as system("start /min sh <system lyxdir>/configure");
> Angus> which fails because J:\MinSys\bin isn't in the cmd.exe's path.
>
> And is it supposed to be in there with a proper installation? I see
> that the msys/mingw faq states
> There is no need to add MSYS's "/bin" to your system PATH
> so I guess the answer is "no".
I believe that this FAQ item is simply trying to say that, when you open a
MinSYS shell, the MinSYS /bin is added to the PATH.
However, we use MinSYS to build lyx. There's no need to run lyx from a
MinSYS shell. Indeed, it's a more representative test to try and run LyX
from a DOS cmd shell. That's essentially what is happening in
system("start /min sh <system lyxdir>/configure");
> Anyway, for a simple installation (like Ruurd's), and the binaries
> will be alongside lyx.exe, so this spaecial PATH element should
> alsways be added (not a a lyxrc variable).
Both Lars and you seem to be arguing that we shouldn't have a
LyXRC::path_prefix variable. I fail to see why this suggestion is
generating so much discussion. It's simple and it'll work. It can be
preset by the lib/configure script. It can be tuned by the user of some
weird and wonderful set up. (Like running LyX from the build directory.)
What's the problem? (No I'm not cross/irritatied. I'm just a little
bemused.)
--
Angus
