| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The config file was used solely for dynamic module paths, but they have
been killed.
|
| |
|
|
|
|
| |
It serves no purpose now.
|
| |
|
|
|
|
| |
We are not building dynamic modules anymore.
|
| |
|
| |
|
|
|
|
| |
Part of Bug 733764 - Support more / free font weights
|
| |
|
| |
|
|
|
|
|
| |
Inspired by:
https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-pango
|
|
|
|
|
| |
Based on:
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-pango/0008-allow-backend-selection.mingw.patch
|
|
|
|
|
| |
From:
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-pango/0006-give-cc-to-gir-scanner.mingw.patch
|
| |
|
|
|
|
|
| |
Needed after this:
https://github.com/behdad/harfbuzz/commit/efe74214bbb68eaa3d7621e73869b5d58210107e
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
g_once_init_leave() does not work on NULL, and just returns... and
all future calls to g_once_init_enter() will block forever.
Happens on Android, so let's just fall back to the C locale if there's
nothing else we can do.
https://bugzilla.gnome.org/show_bug.cgi?id=732276
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit e728c4c3659cc0ead406344b4cf98c0676cb769e.
See previous commit for explanation.
|
|
|
|
|
|
| |
This reverts commit 4901fb74b3c1137d13a6b7e4e8784577c1816e47.
The removed API was added back to HarfBuzz. So, no need for this.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There has been an API change in HB:
-hb_ot_layout_language_get_required_feature_index
+hb_ot_layout_language_get_required_feature
Commit: da132937989acb4d8ca9bd41c79f98750e7dda30
So we need to bump the dependency.
|
|
|
|
| |
Missing colon broke the g-ir-scanner.
|
|
|
|
|
|
| |
A while ago, we added a weight of 1000 to the enumeration, but
neglected to update the allowed values in the documentation.
Fix that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Follow the prevailing practice and put the installed tests
into $libdir/installed-tests/$PACKAGE instead of
$pkglibdir/installed-tests.
|
|
|
|
| |
Oops
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on patch from Chun-wei Fan. Original patch comments:
Improve the thread-safety situation on Windows by only allowing the
pango_aliases_ht GHashTable be populated once.
Pango on Windows is not yet thread-safe, but with the thread safety
patch on Cairo-Win32-Font[1], it does seem that the test program
test-pangocairo-threads does not crash randomly anymore, which seems
to be an improvement.
[1]: https://bugs.freedesktop.org/show_bug.cgi?id=73012
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=695913
|
|
|
|
|
| |
We need to create $(prefix)\etc\pango before trying to create a default
pango.aliases file, otherwise it wouldn't work.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711061
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
Delete libpangocairo.vs10.sourcefiles and
libpangocairo.vs10.sourcefiles.filters once we are done with them, so to
fix make distcheck
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=724006
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Untested.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to Doug Felt:
pango's configure dies with --with-included-modules=yes, because when
have_libthai is true, thai_modules ends up being ",thai-lang", and
all_modules (and included_modules) ends up containing ',,'.
for module in $included_modules;
ends up with module='' and the case $module falls back to default, which
calls as_fn_error.
|