summaryrefslogtreecommitdiff
path: root/build/win32/vs9/pangoft2.vcprojin
Commit message (Collapse)AuthorAgeFilesLines
* Visual Studio builds: Move projects to win32/Chun-wei Fan2017-01-201-170/+0
| | | | | | | This allows one to go down one less level in the directory tree to get to the Visual Studio project files, and so make things more in line with the rest of the GTK+ stack. This also cleans up the Visual Studio 201x projects as there are some items that can be actually combined.
* Export symbols with compiler directives if possibleChun-wei Fan2016-06-291-4/+0
| | | | | | | | | | Add a configure check to see whether compiler directives are available for exporting symbols, and use them if so. Likewise, update the Visual Studio projects and config.h.win32.in to do likewise for Windows builds. We can then drop the .def files that were used to export symbols on Windows builds, which should clean up things a bit.
* MSVC builds: Update PangoFT2-related itemsChun-wei Fan2015-10-081-12/+12
| | | | | | Fix the projects, and consolidate repeated items into the property sheets, as they now need to compile and link against HarfBuzz. Also remove unnecessary lines from the PangoFT2 and PangoCairo project files.
* MSVC Builds: CosmeticsChun-wei Fan2015-04-091-4/+4
| | | | | | | Since we are no longer using the interim Makefile-msvcproj.am way to generate the complete MSVC build files, change all PangoApiVersion to ApiVersion, to be consistent with the other MSVC build files in the GTK+/ Clutter stack.
* MSVC Builds: Restore MSVC 2008/2010 Project GenerationChun-wei Fan2015-04-081-7/+1
| | | | | | | | | | ... in a way that 'make distcheck' (with or without -jN) completes successfully. This uses the common autotools module that was added in a previous commit so that we just need to define the items needed and call the things in there during 'make dist' (or 'make distcheck'), which would have things in a more tidy manner for this. https://bugzilla.gnome.org/show_bug.cgi?id=735039
* Split up the MSVC 2008 Property SheetsChun-wei Fan2013-12-031-6/+4
| | | | ...so that the maintenance of these files would be easier
* Cleanup the Visual Studio 2008 Project FilesChun-wei Fan2013-12-031-2/+4
| | | | | | | 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-181-1/+1
| | | | | 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.
* 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
* | 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.
* Various Visual C++ support updatesChun-wei Fan2011-05-161-227/+53
| | | | | | | | | | | | | -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++ support a bitChun-wei Fan2011-05-161-4/+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.
* Put the PANGO_MODULE_PREFIX defines in the project filesTor Lillqvist2010-03-161-9/+234
| | | | | 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-151-0/+183
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