| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
When gtk-doc regenerated the pango.types file, it includes
get_type functions for platform-specific things that will
cause link failures.
|
|
|
|
|
| |
Users of pango are not generally expected to use gmodule API,
so don't force them all to link against it.
|
|
|
|
|
|
|
|
|
|
| |
It turns out that getting this value as "Int" is incorrect and resulted
in font traits not being returned in some cases. Without traits, an
italic trait is not set, which caused synthetic oblique fonts to be
created when not necessary.
Also use CTFontSymbolicTraits type in the PangoCoreTextFace structure
and do a stricter bit mask check for certainty.
|
| |
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
Now that we get compiler warnings for deprecations, we don't
need to use the G_DISABLE_DEPRECATED hammer anymore.
Bye, bye, build breakage.
|
|
|
|
|
|
|
|
| |
This is using the newly introduce G_DEPRECATED macros
from GLib. Traditional deprecation guards are still in
place.
https://bugzilla.gnome.org/show_bug.cgi?id=661612
|
|
|
|
| |
1.29.4 got released off a side-branch, but bump version here too.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Update the info about the Visual Studio projects as VS2010 projects have
landed into master.
|
|
|
|
|
|
|
|
| |
G_UNICODE_COMBINING_MARK was renamed as G_UNICODE_SPACING_MARK soon after
the GLib 2.29.14 release, so fix that in break.c and pango-ot-info.c.
To support GLib on and before 2.29.14, a convenience definition for
G_UNICODE_SPACING_MARK is defined.
|
|
|
|
|
| |
g_atomic_int_exchange_and_add was deprecated in the GLib gatomic.c rewrite,
for GLib 2.29.6, so use g_atomic_int_add for GLib versions 2.29.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
|
|
|
|
|
|
|
| |
-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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
As requested in bug 403499.
|
|
|
|
|
|
|
|
|
| |
-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.
|
|
|
|
|
|
|
| |
With gcc 4.6.1, I get a build error in pango/ because the C++
parts in harfbuzz have not been compiles with -lPIC. Not sure
if this change is 100% correct, but it makes things build
successfully.
|
|
|
|
|
| |
Backported from HarfBuzz-ng:
http://cgit.freedesktop.org/harfbuzz/commit/?id=cc1a8a938b4c13e76b58825a9e1951c4134e634a
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=656014
|
|
|
|
| |
Tell people not to compile Pango in paths with spaces in them.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=654689
|
|
|
|
|
| |
From:
https://secure.wikimedia.org/wikipedia/en/wiki/Shi_shi_shi_shi_shi
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Fixes a regression from ea702f4 which changed PangoFallbackEngine to be
abstract.
|
|
|
|
|
| |
Commit 02f80c9acdec53f58fef0e12f41363c3c4ea1efe broke the build and was
likely committed untested.
|
|
|
|
|
|
| |
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 :|
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Get rid of entities and use xi:includes instead. This makes the docs build
faster and makes it easier to conditionally include stuff.
|
| |
|
| |
|
|
|
|
| |
This reverts commit 6d1c98aed05ad10111c896708aca86436fc2328a.
|
| |
|
| |
|
| |
|
|
|
|
| |
The syntax doesn't include this, and apparently it confuses gtk-doc.
|