Running LyX/Win32 -dbg init
As promised Jean-Marc here is the output from lyx -dbg init. This is with the 'remainder of Ruurd's changes' patch applied to the current 13x CVS. I've also applied today's two proposals 'mangling temporary file names' and 'determining the name of the LyX system dir'. $ cd qt3/bin $ ~/lyx-13x/build-qt/src/lyx.exe -dbg init Setting debug level to init Debugging `init' (Program initialisation) Initializing LyX::init... Name of binary: J:\MinSYS\home\Angus\lyx-13x\build-qt\src\lyx.exe Path of binary: J:/MinSYS/home/Angus/qt3/bin/ Checking whether LyX is run in place... no System directory search path: J:/MinSYS/home/Angus/qt3/Resources/J \MinSYS\home\Angus\lyx-13x\build-qt\src\lyx.exe/;J:/MinSYS/home/Angus/qt3/share/J:/MinSYS/home/Angus/lyx-13x/build-qt/src/lyx;J:/MinSYS/local/share/lyx-1.3.6cvs LyX Warning! Couldn't determine system directory. Try the '-sysdir' command line parameter or set the environment variable LYX_DIR_13x to the LyX system directory containing the file `chkconfig.ltx'. Couldn't even find the default LYX_DIR. Giving up. Name of binary: Windows-style path but otherwise correct. Path of binary: Unix-style path but actually the directory from which I executed the command to run LyX. System directory search path: Note that there is no ';' between the fist two elements. Note also an entertaining mix of Unix and Windows-style paths. This shouldn't be too hard to fix. I would investigate further, but it takes 24minutes just to link the bloody thing and I'm off to bed ;-) I see that MinGW ships with objcopy. I'll try running that magic that I posted a year ago on the .o files and see if that reduces link times to something manageable. Mañana. #! /bin/sh test $# -gt 0 || exit while (true); do objcopy --set-section-flags .debug_str=contents,debug $1 shift test $# -eq 0 break; done -- Angus
Running LyX/Win32 -dbg init
As promised Jean-Marc here is the output from lyx -dbg init. This is with the 'remainder of Ruurd's changes' patch applied to the current 13x CVS. I've also applied today's two proposals 'mangling temporary file names' and 'determining the name of the LyX system dir'. $ cd qt3/bin $ ~/lyx-13x/build-qt/src/lyx.exe -dbg init Setting debug level to init Debugging `init' (Program initialisation) Initializing LyX::init... Name of binary: J:\MinSYS\home\Angus\lyx-13x\build-qt\src\lyx.exe Path of binary: J:/MinSYS/home/Angus/qt3/bin/ Checking whether LyX is run in place... no System directory search path: J:/MinSYS/home/Angus/qt3/Resources/J \MinSYS\home\Angus\lyx-13x\build-qt\src\lyx.exe/;J:/MinSYS/home/Angus/qt3/share/J:/MinSYS/home/Angus/lyx-13x/build-qt/src/lyx;J:/MinSYS/local/share/lyx-1.3.6cvs LyX Warning! Couldn't determine system directory. Try the '-sysdir' command line parameter or set the environment variable LYX_DIR_13x to the LyX system directory containing the file `chkconfig.ltx'. Couldn't even find the default LYX_DIR. Giving up. Name of binary: Windows-style path but otherwise correct. Path of binary: Unix-style path but actually the directory from which I executed the command to run LyX. System directory search path: Note that there is no ';' between the fist two elements. Note also an entertaining mix of Unix and Windows-style paths. This shouldn't be too hard to fix. I would investigate further, but it takes 24minutes just to link the bloody thing and I'm off to bed ;-) I see that MinGW ships with objcopy. I'll try running that magic that I posted a year ago on the .o files and see if that reduces link times to something manageable. Mañana. #! /bin/sh test $# -gt 0 || exit while (true); do objcopy --set-section-flags .debug_str=contents,debug $1 shift test $# -eq 0 && break; done -- Angus
