lyx_mirror/development/Win32
Lars Gullik Bjønnes 4a7ab830bc Delete all .cvsignore files from trunk
git-svn-id: svn://svn.lyx.org/lyx/lyx-devel/trunk@13208 a592a061-630c-0410-9148-cb99ea01b6c8
2006-02-10 22:09:45 +00:00
..
fakeconfig Michael's "ASCII->Plain Text" changes (bug 1572) 2005-05-21 13:26:13 +00:00
packaging Delete all .cvsignore files from trunk 2006-02-10 22:09:45 +00:00
config.h MSVC compiles out of the box. 2005-05-03 20:32:55 +00:00
fake.bat - Update patch & add fake.bat. LyX win32 VC edition compiles and runs again 2005-02-14 09:40:34 +00:00
libintl.h - Preprepared libintl.h for MSVC compilation 2005-01-23 12:30:03 +00:00
lyx.sln - Adjust to Lars boost::filesystem stuff 2005-01-31 12:25:04 +00:00
lyx.vcproj Remove QPreambleDialogBase.ui from the project 2005-08-19 22:24:44 +00:00
lyxprofile
lyxwin32.c
package.C reflect change in master package.C.in 2005-04-22 22:16:45 +00:00
readme.txt MSVC compiles out of the box. 2005-05-03 20:32:55 +00:00
version.C

To compile using MicroSoft Visual Studio 2003.NET, do this:

1) Checkout Qt/Free from CVS next to lyx-devel and compile.
   See http://kde-cygwin.sourceforge.net/qt3-win32/compile-net.php
   for more info. If you get a linking error about qt-mt3.lib, then
   copy lib/qt-mt333.lib to qt-mt3.lib and rerun configure.

2) Make sure QTDIR is set in your global environment, and QTDIR\bin
   is in your path. Control panel, system, advanced, environment
   variables is your friend on Windows XP.

3) Open the development\win32\lyx.sln file in Visual Studio,
   compile and run. You can probably also use the free version
   of Microsoft's compiler, but I haven't tried that.

Development:

To get a stack-trace for assertions in LyX, make a breakpoint
in src/Boost.C.
To see the output from LyX, add "2> c:\errors.txt" to the command
line in Project, Build properties, Debugging, Command arguments


To run LyX, you need a bunch of generated files from configure.

Run "fake.bat" to copy chkconfig.ltx, lyxrc.defaults, packages.lst
and textclass.lst from fakeconfig to their destination.

At start-up, you might get an assertion about a unix path in
boost::filesystem. You can safely ignore that.