summaryrefslogtreecommitdiff
path: root/build
Commit message (Collapse)AuthorAgeFilesLines
* MSVC Builds: Fix "Installation"Chun-wei Fan2014-08-192-3/+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 2012/2013 Support: Update Property Sheet CreationChun-wei Fan2014-07-011-1/+1
| | | | | | Be a bit more carful when copying and updating the property sheets, so that we don't accidently change fields with '10' in them that are actually not indicating the Visual Studio version.
* Build: Provide Simple Support for MSVC 2012/2013Chun-wei Fan2014-07-014-1/+98
| | | | | | | | | | | As the Visual Studio 2012/2013 are only slightly different from the Visual Studio 2010 projects, we can provide support for them by using scripts to copy the Visual Studio 2010 projects, and update the specific parts as necessary. Thus, there would be little maintenance overhead for these as only the 2010 projects need to be kept up-to-date as a result. This might change when we do get the stack working with WinRT/Metro, but that's going to be another totally different issue.
* MSVC 2010+ Projects: Update "Installation" ProcessChun-wei Fan2014-06-093-26/+42
| | | | | | | | | | | | | | | Currently, due to the way that Visual Studio 2010+ projects are handled, the "install" project does not re-build upon changes to the sources, as it does not believe that its dependencies have changed, although the changed sources are automatically recompiled. This means that if a part or more of the solution does not build, or if the sources need some other fixes or enhancements, the up-to-date build is not copied automatically, which can be misleading. Improve on the situation by forcing the "install" project to trigger its rebuild, so that the updated binaries can be copied. This does trigger an MSBuild warning, but having that warning is way better than not having an up-to-date build, especially during testing and development.
* MSVC Builds: Fix "Installation" for MSVC 2010 and LaterChun-wei Fan2014-04-021-0/+2
| | | | | We need to create $(prefix)\etc\pango before trying to create a default pango.aliases file, otherwise it wouldn't work.
* MSVC Builds: Update Introspection Build ProcessChun-wei Fan2014-02-251-12/+3
| | | | | | | | | | GObject-Introspection was recently changed to support acquiring the name of the DLL from a library (.lib, etc) that was passed into g-ir-scanner on Windows, like the *nix builds, instead of directly passing in the name of the DLL. This updates the introspection build process, so that introspection files for Pango can continue to be properly built.
* build/Makefile-msvcproj.am: Remove Generated Intermediate FilesChun-wei Fan2014-02-211-0/+2
| | | | | | Delete libpangocairo.vs10.sourcefiles and libpangocairo.vs10.sourcefiles.filters once we are done with them, so to fix make distcheck
* MSVC Introspection Build: Fix buildChun-wei Fan2014-01-131-1/+2
| | | | | | | | | | Link and run the dumper program firstly against the build of ATK from the same tarball, then linking to the other dependent libraries which this build of ATK was built against before finally trying to link and run against other existing builds. This is especially important for unstable releases, as APIs are often added and dependent upon during development cycles.
* build/introspection-msvc.mak: Fix Default typelib PathChun-wei Fan2014-01-131-2/+2
|
* MSVC Builds: Rework Introspection BuildChun-wei Fan2014-01-1015-450/+280
| | | | | | | | | | | | | | | | | | | | 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.
* Remove the original "big" MSVC2010 property sheetChun-wei Fan2013-12-031-243/+0
|
* Split up the MSVC 2010 property sheetsChun-wei Fan2013-12-0314-58/+371
| | | | Split up the property sheets so that their maintenance can be simplified
* 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-032-4/+4
| | | | | | 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.
* Visual Studio 2010 Projects: Improve OptimizationChun-wei Fan2013-12-034-0/+10
| | | | | Turn on Whole Program Optimization/Link Time Code Generation for release builds to improve optimization a bit
* 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.
* build/win32/vs10/pango.propsin: Fix .lib installationChun-wei Fan2013-12-031-4/+4
| | | | | Missed out the $(Platform) part when building the FontConfig flavor, so make it up.
* build/win32/vs10/pango.propsin: Improve DLL "installation"Chun-wei Fan2013-12-031-15/+15
| | | | | Make the DLL installation more flexible, as one might still prefer to use the autotools style DLL naming for the Visual Studio builds.
* build/win32/vs10/pangowin32.vcxproj: Clean upChun-wei Fan2013-12-031-4/+4
| | | | | | We don't really need the NoFCDef here, as this DLL has nothing to do with FreeType, like the main Pango DLL. FreeType matters when we build PangoCairo (and the cxx-test.c and pango-view) though.
* build/win32/vs10/pango.vcxprojin: Clean upChun-wei Fan2013-12-031-4/+4
| | | | We don't really need to NoFCDef here, so remove that.
* build/Makefile-msvcproj.am: CleanupChun-wei Fan2013-12-021-2/+0
| | | | Remove lines that were left out in the last commit
* Clean up the Visual Studio 2010 projectsChun-wei Fan2013-12-0213-609/+309
| | | | | | | 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.
* build/win32/vs10/gengir.vcxproj: Add PlatformToolset tagChun-wei Fan2013-11-251-0/+4
| | | | | This makes it easier to upgrade to Visual Studio 2012/2013 formats, like the other *.vcxproj files in Pango.
* Visual Studio Builds: Fix the Debug configsChun-wei Fan2013-03-189-18/+18
| | | | | 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-062-16/+57
| | | | Add commands to be used for building introspection files.
* Update Visual Studio Solution filesChun-wei Fan2013-03-062-0/+16
| | | | | | | 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-067-38/+551
| | | | | | | | | | | | | 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
* Prepare Visual Studio 2010 projects for Visual Studio 2012Chun-wei Fan2013-01-186-10/+41
| | | | | | | | | | | | | | 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 Visual C++ 2010 solutionsChun-wei Fan2012-12-132-2/+2
| | | | | Cosmetic changes, so that the .sln files will have the same headers across the board
* Visual C++: Remove the "static" property sheetsChun-wei Fan2012-08-242-381/+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-235-0/+596
| | | | | | | | | | | | | -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-213-5/+5
| | | | | 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-202-14/+0
| | | | Remove nonexisting files from EXTRADIST, this was breaking distcheck.
* Update build/ to include git.mkBehdad Esfahbod2012-08-204-0/+8
|
* Fix the pangoft2 Visual C++ projectsChun-wei Fan2012-08-203-129/+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-163-3/+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-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.
View Lorry Controller Status