| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
| |
-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
|
|
|
|
| |
Make the include paths and predefined macros consistent across the board.
|
|
|
|
|
| |
Now the code links directly to usp10.lib, so add that in the project
files.
|
|
|
|
| |
It has to be possible to run "make dist" also in an unpacked tarball.
|
|
|
|
|
| |
Put the PANGO_MODULE_PREFIX defines in the project files instead of
having them behind an ifdef in the source files.
|
| |
|
|
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.
|