summaryrefslogtreecommitdiff
path: root/build/win32/vs9
Commit message (Collapse)AuthorAgeFilesLines
* MSVC Builds: Rework Introspection BuildChun-wei Fan2014-01-104-114/+0
| | | | | | | | | | | | | | | | | | | | The current approach of building the introspection files for Pango works, but is often cumbersome as one needs to set many environmental variables before launching a solution file, which runs a Windows batch script to generate the .gir/.typelib files. It was also possible to hand-run the batch script from the Visual Studio command prompt, but even more environmental variables need to be set. This changes the approach to build the introspection files using an NMake Makefile (but elimating from the Visual Studio Project Files the part to build the introspection files) to: -Make it clearer to the person building the introspection files what environmental variables are needed, specifically for PKG_CONFIG_PATH and MINGWDIR and CFG (formerly CONF). Setting stuff like VSVER, PLAT and BASEDIR is no longer required, which was a bit clunky. -Allows some more easier flexibility on the build of the intropsection files.
* MSVC 2008 Projects: More cleanupsChun-wei Fan2013-12-052-12/+0
| | | | | | We don't have the *_FC configs in the Pango and PangoWin32 projects anymore, so get rid of all remaining traces of them in these projects, like the MSVC 2010 ones.
* Split up the MSVC 2008 Property SheetsChun-wei Fan2013-12-0314-238/+268
| | | | ...so that the maintenance of these files would be easier
* build/win32/vs*/README.txt: Update build informationChun-wei Fan2013-12-031-2/+2
| | | | | | As there is no longer a pango_fc.sln solution file, tell the people to use the *_fc configs if building PangoFT2 and PangoCairo with FreeType/ FontConfig support with the Visual Studio Projects is desired.
* Cleanup the Visual Studio 2008 Project FilesChun-wei Fan2013-12-0310-392/+177
| | | | | | | Combine the non-PangoFT2 and PangoFT2 builds into one single solution file and remove configs in the Pango and PangoWin32 projects that aren't really necessary. Also use Link Time Code Generation for release builds to improve optimization a bit.
* Visual Studio Builds: Fix the Debug configsChun-wei Fan2013-03-184-9/+9
| | | | | We need to link to the Debug CRT for debug configs, not the release CRTs, as linking to different CRTs will cause trouble during debugging.
* Update Visual Studio property sheetsChun-wei Fan2013-03-061-6/+27
| | | | Add commands to be used for building introspection files.
* Update Visual Studio Solution filesChun-wei Fan2013-03-061-0/+10
| | | | | | | Integrate the utility project files to build the introspection files. This is not built by default, so one may choose to build the introspection files if he/she chooses
* Visual Studio builds: Support building introspection filesChun-wei Fan2013-03-062-13/+91
| | | | | | | | | | | | | Add Windows .bat and Python utility script to call g-ir-scanner to build the introspection files for Pango/MSVC builds. This will read from pango/Makefile.am to determine the source and header files to process using Python REGEX capabilities, so the autotools files won't have to be updated except to distribute the necessary files under build/win32. Also add utility Visual Studio 2008/2010 projects to call the Windows .bat to create the introspection files. https://bugzilla.gnome.org/show_bug.cgi?id=692255
* Visual C++: Remove the "static" property sheetsChun-wei Fan2012-08-241-158/+0
| | | | | | The property sheets now have their header listings for "installation" filled in during make dist, so we don't need to keep the static pango property sheets around.
* autotools: Re-enable and enhance the completion of MSVC projectsChun-wei Fan2012-08-232-0/+149
| | | | | | | | | | | | | -Isolate the creation of full MSVC projects for pango, pangoft2 and pangocairo in a seperate build/Makefile-msvcproj.am, so it can be included and used elsewhere. -Update the Makefile.am's in pango/ and pango/mini-fribidi to include and use build/Makefile-msvcproj.am to create the MSVC project files -Use templates for the property sheets so that the listings of header files to "install" can be filled in using build/Makefile-msvcproj.am, to simplify future maintenance. -Re-enable the distribution of the created project files and property sheets
* Update pango Visual C++ project templatesChun-wei Fan2012-08-211-1/+1
| | | | | Simplify the inclusion of the mini-fribidi sources a bit, so we can use the -I flag to the preprocessor when creating the projects
* Neuter win32 build stuffMatthias Clasen2012-08-201-4/+0
| | | | Remove nonexisting files from EXTRADIST, this was breaking distcheck.
* Update build/ to include git.mkBehdad Esfahbod2012-08-201-0/+2
|
* Fix the pangoft2 Visual C++ projectsChun-wei Fan2012-08-201-56/+0
| | | | | Many of the module sources have been removed for pangoft2, so remove them from the projects.
* Merge branch 'harfbuzz-ng-external'Behdad Esfahbod2012-08-161-1/+0
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: configure.in docs/tmpl/text-attributes.sgml modules/arabic/arabic-ot.c modules/indic/indic-ot.c pango/opentype/Makefile.am pango/opentype/hb-blob.c pango/opentype/hb-buffer-private.h pango/opentype/hb-common.h pango/opentype/hb-ot-layout-gsubgpos-private.hh pango/opentype/hb-private.h pango/pango-ot-info.c
* | Fix "install" paths in VS property sheetsChun-wei Fan2012-03-151-1/+1
| |
* | Update VS property sheetsChun-wei Fan2011-10-171-1/+1
| | | | | | | | | | 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-161-2/+5
| | | | | | | | | | | | | | -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
* | 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-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