summaryrefslogtreecommitdiff
path: root/build
Commit message (Collapse)AuthorAgeFilesLines
* Fix "install" paths in VS property sheetsChun-wei Fan2012-03-152-2/+2
|
* Update VS property sheetsChun-wei Fan2011-10-172-2/+2
| | | | | Say farewell to G_DISABLE_DEPRECATED and the build breakages that it causes. We now have warnings when we make use of deprecated GLib items
* Update VS2008 PangoFT2 projectChun-wei Fan2011-09-251-4/+4
| | | | | | | | This project will require the use of stdint.h, which is not shipped with VS2008 (but is shipped with VS2010), so define HAVE_STDINT_H for all settings in this project so that the stdint.h bundled in $(srcroot)/build/win32/vs9 will be used when HarfBuzz and FontConfig is being used.
* VS support: Fix VS2008/2010 property sheetsChun-wei Fan2011-09-162-5/+11
| | | | | | | -Seperate intermediate folders for each project to remove redundant VS warnings/errors -Don't create a folder for pango.aliases if the folder already exists -Don't create pango.aliases if it already exists
* VS2010 support: Update README.txtChun-wei Fan2011-09-161-88/+96
| | | | | | | -This file should have Windows EOL -Tell people about GNOME Live! page for steps to building Pango with MSVC (and the GTK+ stack) -Fix some errors in some of the words used here.
* Bug 653985: Fix the VS2010 Pangowin32 projectChun-wei Fan2011-09-161-1/+10
| | | | | Define the PANGO_MODULE_PREFIX in the project, as was done with the VS9 project in commit 552ffc231.
* VS 2010 support: Fix EOL of .sln filesChun-wei Fan2011-09-162-120/+120
| | | | The .sln files need to have Windows EOL.
* bgo# 650456 Visual C++ 2010 support-README.txtChun-wei Fan2011-09-161-0/+88
|
* bgo# 650456: Visual C++ 2010 Project FilesChun-wei Fan2011-09-1614-0/+1940
| | | | | | | | | | | | | These are the VS 2010 project files themselves... As in the last patch, project and filter files for pango, pangocairo and pangoft2 are templates so that they are filled in during "make dist", which the resulting full project/filter files are distributed with the templates Yeah, I know there are 2 sets of projects/filters for pangocairo, but it is needed to accomodate the options for the dependency on fontconfig/pangoft2 on VS2010. That's life with VS2010...
* bgo# 650456: Visual C++ 2010 support-autotoolsChun-wei Fan2011-09-162-1/+25
| | | | | | | | | | | Update the autotools files for: -Creation of the full VS 2010 project/filter files for pango, pangocairo and pangoft2 from the templates during "make dist", so that the source file list can be made up-to-date with each release-this will simplify maintenance, as this is what is done for the VS 2008 project files. -Dist the VS 2010 files (with the templates) and related items
* Updated README.win32 and VS9 Readme.txtChun-wei Fan2011-08-311-0/+5
| | | | | | | | | -Set README.win32 to have Windows EOL -Updated README.win32 regarding the situation of modules on Windows under different build approaches. -Tell people in both Readme files about the GNOME Live! page that describes building Pango and its dependencies with Visual Studio in better detail.
* Update VS 2008 README.txtChun-wei Fan2011-07-251-1/+4
| | | | Tell people not to compile Pango in paths with spaces in them.
* Bug 653985 - Pango 1.29.x make GTK3-demo.exe crashed in WindowsBehdad Esfahbod2011-07-111-1/+10
| | | | | | | | | Similar to d9e254f which changed the rest of the modules, moved the PANGO_MODULE_PREFIX define from basic-win32.c to the VS9 project file to avoid breaking autotools build. Fixes basic-win32 module loading when pango is built with autotools + MinGW.
* Attempt to correct EOL on VS2008 solutionsChun-wei Fan2011-06-292-149/+149
| | | | | | I realized that I needed to set autocrlf=false on my Windows side ... ugh... These are the files that must have CRLF line endings to work correctly :|
* 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-1611-322/+647
| | | | | | | | | | | | | -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-164-4/+6
| | | | | | | | -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 a couple of files accidentally left out in previous commitTor Lillqvist2010-03-152-0/+2
|
* 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