| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We need to create $(prefix)\etc\pango before trying to create a default
pango.aliases file, otherwise it wouldn't work.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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 property sheets so that their maintenance can be simplified
|
|
|
|
| |
...so that the maintenance of these files would be easier
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Turn on Whole Program Optimization/Link Time Code Generation for release
builds to improve optimization a bit
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Missed out the $(Platform) part when building the FontConfig flavor, so
make it up.
|
|
|
|
|
| |
Make the DLL installation more flexible, as one might still prefer to use
the autotools style DLL naming for the Visual Studio builds.
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
We don't really need to NoFCDef here, so remove that.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
This makes it easier to upgrade to Visual Studio 2012/2013 formats, like
the other *.vcxproj files in Pango.
|
|
|
|
|
| |
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.
|
|
|
|
| |
Add commands to be used for building introspection files.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Cosmetic changes, so that the .sln files will have the same headers across
the board
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-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
|
|
|
|
|
| |
Simplify the inclusion of the mini-fribidi sources a bit, so we can use
the -I flag to the preprocessor when creating the projects
|
|
|
|
| |
Remove nonexisting files from EXTRADIST, this was breaking distcheck.
|
| |
|
|
|
|
|
| |
Many of the module sources have been removed for pangoft2, so remove them
from the projects.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
|
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| | |
-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
|
| |
| |
| |
| |
| |
| |
| | |
-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.
|
| |
| |
| |
| |
| | |
Define the PANGO_MODULE_PREFIX in the project, as was done with the
VS9 project in commit 552ffc231.
|
| |
| |
| |
| | |
The .sln files need to have Windows EOL.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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...
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
-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.
|
| |
| |
| |
| | |
Tell people not to compile Pango in paths with spaces in them.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
| |
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 :|
|
|
|
|
| |
accidently removed that during my last changes...doh.
|
|
|
|
| |
Make pathnames Windows-like... missed them just now. doh.
|
|
|
|
|
| |
Make the instructions to compile Pango with Visual C++
clearer.
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-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.
|