summaryrefslogtreecommitdiff
path: root/build/win32/vs10/pango.vcxprojin
Commit message (Collapse)AuthorAgeFilesLines
* Visual Studio builds: Move projects to win32/Chun-wei Fan2017-01-201-180/+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 2010+ builds: Do not explicitly use /LTCGChun-wei Fan2015-11-121-2/+0
| | | | | | | | | This partially reverts 03e60dc. As we now ensure that items using GResources and GConstructors are always referenced so that the linker does not optimize them out in a default Release build, we no longer need to enforce the use of /LTCG, so /LTCG:incremental will work as well.
* MSVC release builds: Ensure that /LTCG is usedChun-wei Fan2015-10-231-4/+6
| | | | | | | | | MSVC 2015 changed its default link-time code generation setting to /LTCG:incremental, which causes problems if /opt:noref is to be used, meaning that some code will be optimized out by the linker. Avoid this situtation here by enforcing the use of /LTCG for MSVC 2010+ builds.
* MSVC projects: Ensure files have UNIX line endingsChun-wei Fan2015-10-081-1/+1
| | | | ...except for the .sln and the README.txt files, to ease maintainenance.
* 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.
* pango.vcxproj: Fix MSVC 2010+ BuildChun-wei Fan2015-04-081-4/+4
| | | | | The command macro for copying config.h.win32 to config.h was wrong due to a leftover when copying the rule. Fix that, oops.
* MSVC Builds: Restore MSVC 2008/2010 Project GenerationChun-wei Fan2015-04-081-2/+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
* MSVC Builds: Use Custom Build RulesChun-wei Fan2015-04-071-16/+18
| | | | | | 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.
* Split up the MSVC 2010 property sheetsChun-wei Fan2013-12-031-4/+8
| | | | Split up the property sheets so that their maintenance can be simplified
* Visual Studio 2010 Projects: Improve OptimizationChun-wei Fan2013-12-031-0/+2
| | | | | Turn on Whole Program Optimization/Link Time Code Generation for release builds to improve optimization a bit
* build/win32/vs10/pango.vcxprojin: Clean upChun-wei Fan2013-12-031-4/+4
| | | | We don't really need to NoFCDef here, so remove that.
* Clean up the Visual Studio 2010 projectsChun-wei Fan2013-12-021-148/+2
| | | | | | | Use a single solution file for the non-PangoFT2 and PangoFT2 builds, and use a single PangoCairo project for these builds too. Also get rid of configurations that we don't really need in the Pango and PangoWin32 projects.
* Visual Studio Builds: Fix the Debug configsChun-wei Fan2013-03-181-2/+2
| | | | | 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.
* Prepare Visual Studio 2010 projects for Visual Studio 2012Chun-wei Fan2013-01-181-1/+8
| | | | | | | | | | | | | | This adds a PlatformToolset tag in the project configs so that we can provide support for Visual Studio 2012 with relative ease as the format of the VS 2012 projects are only slightly different from their VS 2010 counterparts. We can then use a script like the one used in GLib[1] to copy the VS2010 projects and replace the necessary tags to create the VS2012 projects. This also cleans up the projects and property sheets, as there were some unwanted/unneeded entries in them. [1]: http://git.gnome.org/browse/glib/commit/?id=76cecf061b377d30e5422cdddb1fb9d19c52421d
* Update pango Visual C++ project templatesChun-wei Fan2012-08-211-2/+2
| | | | | Simplify the inclusion of the mini-fribidi sources a bit, so we can use the -I flag to the preprocessor when creating the projects
* bgo# 650456: Visual C++ 2010 Project FilesChun-wei Fan2011-09-161-0/+316
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...
View Lorry Controller Status