Asger Kunuk Ottar Alstrup wrote: > On Wed, 15 Dec 2004, Ruurd Reitsma wrote: > >> With MSVC, I use a wrapper tool which makes cl.exe grog gcc arguments. >> Saves you the trouble of maintaining your own project files, besides the >> autotools stuff. Building then takes place in a normal cygwin >> environment, and a native binary comes out. > > Could you maybe wrap that wrapper script up, along with a README for how > to do this? I would suggest to add this to the CVS distribution. > > But I'd prefer to have a completely native Windows build environment > without the requirement of cygwin. That would expand the developer base a > lot. Would it be enough to check in the genereated Makefiles and config.h > files? > > How well does a native Qt Win32 work? > > Regards, > Asger
Hi, Asger. Hi, Peter. FWIW, I'm incorporating Ruurd's changes to the LyX sources back into both the 13x and 14x trees. So, although the build process will still depend on MinGW and MinSYS (no need for cygwin), the result will be a fully functional and native LyX on Win32 using the port of Qt to Win32 by the cygwin-kde people. Ruurd has a (small) additional patch that enables the sources to be compiled with MSVC rather than gcc. Status of incorportating Ruurd's changes: * Much of the 'trivial' stuff is in the 13x and 14x trees already. * Some configure guards need to be written for Win32's POSIX compatibility layer. Thinks like mkdir have slightly different interfaces. * Some configure guards need to be written for file system stuff such as symbolic links. * The code to launch and kill child processes needs to be rewritten using the native Win32 API. The real difficulty in having a completely native Windows build environment will be the maintenance of config.h. I think a sensible middle ground is to use MinSYS (apparently it doesn't require MinGW) to provide the environment to build config.h. -- Angus
