>>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> - in set_build_lyxdir, are you sure there is a real need for >> following symlinks? Since this is basically just a convenience >> feature for programmers, I think we can keep it simple. What >> examples of use did you have in mind? Angus> $ cd $HOME/bin $ ln -s $HOME/lyx/13x/build-xforms/src/lyx Angus> xlyx13x $ cd $ xlyx13x Angus> That works at the moment for LyX 1.3.x but does not work for Angus> LyX 1.4.x. I've always found it useful, so why not continue it? Fair enough. >> - in general, there is AFAIK no need for special casing EMX and >> Cygwin in directory selection, since they use a unix-like layout. >> The only thing to look for are file name conversions. Angus> Thanks for that. I know nothing at all about OS/2 so any and Angus> all info will be received most gratefully. ... and that's partly what I meant by advocating to get rid of most of cygwin explicit support. This and EMX strive to be posix-like. >> For LyX/Win, use the directory which holds the binary Angus> Hmmm. Or perhaps add a directory Resources to the directory Angus> that holds the binary, like the Mac? I think the canonical (or usual) windows name is "Data", but you may want to check that on a few programs. >> Also, an advantage of avoiding the symlink following code on win32 >> is that it will avoid a case of using posix-only features (lstat) >> on a system that lacks them. Angus> I don't think that's so important as the support code will Angus> remain anyway, just will be protected with HAVE_LSTAT. I was thinking about the headers that one has to add to make msvc behave. I think LyX/Win should be able to work without them, since the corresponding features do not work. JMarc
