summaryrefslogtreecommitdiff
path: root/build/win32/vs9
Commit message (Collapse)AuthorAgeFilesLines
* Dist the Visual C++ 2008 README.txt fileChun-wei Fan2011-05-251-1/+2
| | | | accidently removed that during my last changes...doh.
* Minor updates to Visual C++ 2008 README.txtChun-wei Fan2011-05-181-4/+4
| | | | Make pathnames Windows-like... missed them just now. doh.
* Update Visual C++ 2008 README.txtChun-wei Fan2011-05-181-2/+55
| | | | | Make the instructions to compile Pango with Visual C++ clearer.
* Update Visual C++ 2008 property sheetChun-wei Fan2011-05-171-0/+6
| | | | | | Create a pango.aliases file in $(OutDir)etc\pango during the "install" phase. The contents of the file is identical to the one that is suggested in README.win32
* Various Visual C++ support updatesChun-wei Fan2011-05-1610-321/+682
| | | | | | | | | | | | | -Move the stub stdint.h back into the vs9 folder as stdint.h is shipped with Visual C++ 2010, and update the corresponding Makefile.am's accordingly -Add new solution to build Pango with FontConfig-the former solution file will build Pango without FontConfig. This is to simplify the use of the GTK+ stack as many will probably not use FontConfig on Windows, therefore this is to reduce the number of dependencies -Added configurations in Pango, PangoWin32, PangoCairo regarding FontConfig (To make sure their configurations are consistent across the board) -Cleaned up the various project files for a bit.
* Update Visual C++ property sheetChun-wei Fan2011-05-161-3/+6
| | | | | | Force the use of the pre-generated sources and headers, so that language/script modules can be used directly and correctly from the main Pango/PangoWin32/PangoFT2 DLL(s)
* Update Visual C++ support a bitChun-wei Fan2011-05-163-41/+4
| | | | | | | | -Move the stub unistd.h and stdint.h required up a level to ease the addition of Visual C++ 2010 support -Dist the Visual C++-stub unistd.h and stdint.h -Update the pangoft2 project again to reflect the change in the location of the Visual C++-stub headers
* Update pangoft2 Visual C++ projectChun-wei Fan2011-05-161-3/+6
| | | | Make the include paths and predefined macros consistent across the board.
* Update pangowin32 Visual C++ projectChun-wei Fan2011-05-161-0/+4
| | | | | Now the code links directly to usp10.lib, so add that in the project files.
* Dist also the .vcprojin filesTor Lillqvist2010-03-161-0/+3
| | | | It has to be possible to run "make dist" also in an unpacked tarball.
* Put the PANGO_MODULE_PREFIX defines in the project filesTor Lillqvist2010-03-162-11/+286
| | | | | Put the PANGO_MODULE_PREFIX defines in the project files instead of having them behind an ifdef in the source files.
* Add solution and project files for Visual Studio buildsTor Lillqvist2010-03-1511-0/+1053
The VS files are kept in build/win32/vs9, the same relative location as in GLib, mostly for historical reasons. Update README.win32 to reflect the VS possibility. Include the VS solution and project files in the tarball when doing a release. To avoid having to list source files in several locations, generate files listing source files at "make dist" time in the corresponding source directories. Use the C preprocessor to preprocess .vcprojin files that include said list files into the actual .vcproj project files. Provide a rc file for the pangocairo DLL, too. Construct and provide in the tarball a pregenerated config.h.win32 which can be used as config.h when building with Visual C without running any configure script. Provide pregenerarated module-defs.h.win32, module-defs-lang.c.win32 files too. Define PANGO_MODULE_PREFIX appropriately in the relevant module source files if not available from the compilation command line. Update module-defs-fc.c.win32 and module-defs-win32.c.win32 to match what the configure script provides.
View Lorry Controller Status