Abdelrazak Younes wrote: > Peter Kümmel wrote: >> Bo Peng wrote: >>>> $ cat README.W32 >>>> You may build the Win32 version of Aiksaurus with MSVC. Other >>>> compilers should >>>> work but makefiles and project files have not been provided. >>>> >>>> For command line junkies - simply >>>> nmake -f Makefile.msc >>>> >>>> For DevStudio - go to win/src directory and open up the Aiksaurus.dsw >>>> >>>> Then build. >>> I tried. Did not work. The project file is also broken. I tried to >>> build the library using scons, and it was super easy (only 5 or so >>> source files) because its config.h is a subset of lyx config.h, >>> >>> Now, what I can offer (already in my local branch) is that I can >>> provide scons options like aiksaurus_src_path (done) and >>> aspell_src_path (progressing) so that lyx/scons can build the >>> libraries just like gettext and boost. I am not sure if people will >>> welcome this. After all, it is *not* lyx's responsibility to build >>> them and keeping these parts up to date is difficult, although, on the >>> positive side, they can be useful, and can be safely ignored. >>> >>> Cheers, >>> Bo >> >> The best way would be to add the build system to the original project, >> or when this is not possible only to host the scons files in the lyx >> svn. >> >> If you need help with aspell, just ask, here I've a lyx build with a >> cvs-aspell, I'm still using cmake, but it should not be a problem to >> write a scons script because no configuring is required. I've also >> posted to the aspell list, if they could apply my minimal changes. >> >> If you currently use the 0.60.4 release you should really have a look >> at the cvs version, it's much cleaner code, and the Makefile.am is >> much more readable. > > Interesting news Peter. What about the dictionnaries... are they > relocatable on windows with the CVS version? >
I'm sorry, I've only managed to handle the C++ stuff, the rest is a small mystery to me. I need more help and instructions to come forth. >> And here an idea for your scons scripts. The cmake file I've checked >> in today are looking for iconv and aspell by default, and when they >> are found then the build system uses them, if not then they disable >> them, no more user interaction by passed parameters. You could force >> the usage so that the configure process stops but then you have add >> an additional flag. But this approach breaks maybe the ./configure >> philosophy, so it's just an idea. > > I think it is a good idea. > > Abdel. > >
