| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
The length is an unsigned int, and it is already enforced that it must
be greater or equal to 0 in this source file, so fix the type declaration.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Make its entries more consistent to the autotools-generated config.h.in,
and update MODULE_VERSION to 1.8.0, as that was missed.
|
|
|
|
|
|
|
|
|
|
| |
parse_int() is called by pango_parse_enum(), which permits the enum
string to be NULL. This string is passed directly through to parse_int()
and then to strtol(), which is tagged as nonnull.
Found by scan-build.
https://bugzilla.gnome.org/show_bug.cgi?id=719549
|
|
|
|
| |
Remove lines that were left out in the last commit
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Patch from Rafał Mużyło.
|
|
|
|
|
|
|
|
| |
When handling PANGO_ATTR_SCALE on a font description with an absolute
size, properly preserve the absolute flag when setting the scaled
size.
https://bugzilla.gnome.org/show_bug.cgi?id=708778
|
| |
|
|
|
|
| |
PANGO_GRAVITY_NORTH instead of PANGO_GRAVITY_SOUTH?
|
|
|
|
|
|
| |
The annotation for pango_layout_set_attributes should be
'transfer none', not 'transfer full'. Pointed out in
https://bugzilla.gnome.org/show_bug.cgi?id=707874
|
|
|
|
|
|
|
|
|
|
|
| |
layouts get initialized with text == NULL as an optimization (avoid a
malloc). But pango_layout_set_text (layout, NULL, 0); will set the text
to "", so it is impossible to set a NULL text.
Fxies crashers in various places that assume NULL return values never
happen.
https://bugzilla.gnome.org/show_bug.cgi?id=707659
|
|
|
|
|
|
|
|
|
| |
Since pango_scan_int() would return FALSE if the scanned value was over
INT_MAX; and the reference out value's type is an int, (n > INT_MAX)
test is unecessary.
If pango_scan_int() behavior was to be changed to accept long
int, an explicit test should be added (or the PangoAttrSize
type updated to handle long int too).
|