summaryrefslogtreecommitdiff
path: root/build/win32/vs9
Commit message (Collapse)AuthorAgeFilesLines
* Visual Studio builds: Move projects to win32/Chun-wei Fan2017-01-2015-1554/+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-294-20/+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.
* Visual Studio builds: Clean up PangoCairo build filesChun-wei Fan2016-06-222-10/+10
| | | | | Define HAVE_CAIRO_FREETYPE in the property sheets instead of disabling it via conditional compilation, which makes things a bit neater.
* PangoCairo MSVC builds: Look for headers in $(prefix)/include/cairoChun-wei Fan2016-06-222-4/+12
| | | | | Cairo's headers could be in $(prefix)/include/cairo, so look for the headers from there as well.
* Visual Studio builds: Generate .pc filesChun-wei Fan2016-04-212-8/+94
| | | | | | | If python can be found at $(PythonPath)\python.exe (x86 builds) or $(PythonPathX64)\python.exe (x64 builds), generate .pc files for Pango, as appropriate with the build config chosen. This will make building introspection on Visual Studio easier with packages that depend on Pango.
* Visual Studio builds: Have package version in the projectsChun-wei Fan2016-04-211-4/+24
| | | | | This is used to generate the .pc files to make generating introspection files easier for packages that depend on Pango.
* MSVC builds: Re-arrange GLib include pathsChun-wei Fan2016-03-021-1/+1
| | | | We ought to include the platform-neutral headers first...
* MSVC builds: Update PangoFT2-related itemsChun-wei Fan2015-10-083-29/+34
| | | | | | 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: Clean up PangoWin32 projects a bitChun-wei Fan2015-10-081-1/+0
| | | | Remove unneeded AdditionalIncludeDirectories directive.
* MSVC Builds: CosmeticsChun-wei Fan2015-04-097-36/+36
| | | | | | | 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: Fix Header "Installation"Chun-wei Fan2015-04-091-0/+1
| | | | | | Create the directory where the headers should be copied. I did not notice this as there was always $(GlibEtcInstallRoot)\vs$(VSVER)\$(PLAT)\include\pango-1.0\pango. Oops.
* MSVC Builds: Restore MSVC 2008/2010 Project GenerationChun-wei Fan2015-04-086-55/+31
| | | | | | | | | | ... 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
* MSVC Builds: Use Custom Build RulesChun-wei Fan2015-04-072-44/+45
| | | | | | Use a custom build rule for the copying of config.h.win32 to config.h, and reflect on the changes on the module source files for the Arabic and Indic line breaks.
* [win32] Unbreak make distcheckBehdad Esfahbod2015-04-041-3/+4
| | | | Win32 maintainer, please...
* MSVC Builds: Rename "Install" ProjectChun-wei Fan2015-03-063-4/+4
| | | | | | Rename the install projects to pango-install, so that they can be easier integrated into grand solution files that are used to build items, such as the entire GTK+ or Clutter stack.
* MSVC Builds: "Install" the .pdb filesChun-wei Fan2015-03-041-10/+11
| | | | | To make it easier for people to develop and debug Pango on Windows, especially as the builds already generate the .pdb's.
* MSVC Builds: Speed Up Release BuildsChun-wei Fan2015-03-041-0/+1
| | | | | | | This adds the /MP option to the compiler, which can cut down on the build time of release builds by quite a bit, by using multi-processor or multi-core capabilities. This will, however, emit a brief warning with debug builds, but the code will otherwise build normally.
* MSVC Builds: Fix "Installation"Chun-wei Fan2014-08-191-1/+1
| | | | | | Make sure we only try to create the directory for pango.aliases if that file didn't exist. This cleans things up a little, and avoids weird MSBuild batch errors.
* 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.
View Lorry Controller Status