Darkvater 53f48bbd4d (svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better). ...

-Remove: [os/2] Relic project file remains from watcom

2007-03-10 00:25:54 +00:00

..

openttd.xcode

(svn r7759) -Merge: makefile rewrite. This merge features:

2007-01-02 19:19:48 +00:00

generate

(svn r8948) -Change: some sed implementations have problems with \n so rewrite r8832 using awk

2007-02-28 23:52:04 +00:00

langs_vs80.vcproj

(svn r8832) -Change: rewrite the solution file generator a little so it makes project files that look more like the ones generated by respectively MSVC2003 and MSVC2005.

2007-02-21 17:59:34 +00:00

langs_vs80.vcproj.in

(svn r8832) -Change: rewrite the solution file generator a little so it makes project files that look more like the ones generated by respectively MSVC2003 and MSVC2005.

2007-02-21 17:59:34 +00:00

langs.vcproj

(svn r8832) -Change: rewrite the solution file generator a little so it makes project files that look more like the ones generated by respectively MSVC2003 and MSVC2005.

2007-02-21 17:59:34 +00:00

langs.vcproj.in

(svn r7759) -Merge: makefile rewrite. This merge features:

2007-01-02 19:19:48 +00:00

openttd_vs80.sln

(svn r8832) -Change: rewrite the solution file generator a little so it makes project files that look more like the ones generated by respectively MSVC2003 and MSVC2005.

2007-02-21 17:59:34 +00:00

openttd_vs80.vcproj

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00

openttd_vs80.vcproj.in

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00

openttd_vs80.vcproj.user

(svn r7759) -Merge: makefile rewrite. This merge features:

2007-01-02 19:19:48 +00:00

openttd.sln

(svn r8832) -Change: rewrite the solution file generator a little so it makes project files that look more like the ones generated by respectively MSVC2003 and MSVC2005.

2007-02-21 17:59:34 +00:00

openttd.tgt

(svn r7759) -Merge: makefile rewrite. This merge features:

2007-01-02 19:19:48 +00:00

openttd.vcproj

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00

openttd.vcproj.in

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00

strgen_vs80.vcproj

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00

strgen.vcproj

(svn r9082) -Codechange: [win32] Update VS2003 and VS2005 project files to use the same outpath, and build in UNICODE mode. When making a release it is probably better to make two binaries, one without UNICODE, the other with, guaranteeing full Win9x compatibility (UNICODE with MSLU also works, without it's even better).

2007-03-10 00:25:54 +00:00