| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Meson is a meta build system that is:
- fast
- simpler to understand and use
- portable to multiple platforms through different backends
- well integrated with the GNOME platform
- well maintained
Using Meson allows us to build Pango much more quickly, and on all the
platforms we currently target, without any loss of functionality,
compared to Autotools.
Some timing comparisons with hot ccache for both build systems:
* autogen.sh: * meson
real 0m11.149s real 0m2.525s
user 0m8.153s user 0m1.609s
sys 0m2.363s sys 0m1.206s
* make -j$(($(nproc) + 2)) * ninja
real 0m9.186s real 0m3.387s
user 0m16.295s user 0m6.887s
sys 0m5.337s sys 0m1.318s
--------------------------------------------------------------
* autotools * meson + ninja
real 0m27.669s real 0m5.772s
user 0m45.622s user 0m8.465s
sys 0m10.698s sys 0m2.357s
System: Intel Core i7-7500U, SSD, 16GB of RAM
|
|
|
|
|
|
| |
While `.C` is a valid GCC extension for C++ files, it only works for
case sensitive file systems. Let's use `.cpp`, like the rest of the
planet does.
|
|
|
|
|
|
|
| |
g_assert gets neutered by --enable-debug=no, which is not what
we want in tests. Use g_assert_true instead.
https://bugzilla.gnome.org/show_bug.cgi?id=755126
|
|
|
|
| |
GLib enforces this now.
|
|
|
|
|
| |
Exposes an assertion failure:
https://bugzilla.gnome.org/show_bug.cgi?id=541608
|
| |
|
|
|
|
|
| |
Apparently libthai is not threadsafe. This crashes
right away if libthai is enabled...
|
| |
|
| |
|
|
|
|
| |
Fails right now. Fix coming.
|
| |
|
|
|
|
|
|
|
| |
coverity says: Using uninitialized value "index2". It didn't
notice that the only time we can reach the index = index2
assignment with index2 still uninitialized is when we are
never going to look at index again.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
These tests exercise PangoAttribute, PangoAttrList and
PangoAttrIterator apis.
|
|
|
|
| |
These will be reused later.
|
|
|
|
|
| |
Update the expected output of the layout tests to the previous
change.
|
|
|
|
|
| |
For some reason (that I haven't been able to track down), this
fails in the installed tests on build.gnome.org.
|
|
|
|
| |
This just a small beginning, much more is needed here.
|
|
|
|
|
|
| |
For some reason, the test-layout test does not show the
font size when run on build.gnome.org. Try harder to make
it use the Cantarell 11 font that I want it to use.
|
|
|
|
|
| |
We see the 'ellipsized' analysis flag in the output now,
as we should.
|
|
|
|
|
| |
Run diff over the output to give a meaningful error if the
comparison fails.
|
|
|
|
|
|
| |
This tests works similar to the markup parser tests -
we populate a layout with known data, and then compare
a dump of its properties with expected output.
|
|
|
|
|
|
|
|
|
|
| |
This test is modeled after the GMarkup parser tests in GLib.
Test file with a name ending in .markup can be dumped in
tests/markups/, and tests/markup-parse can be used to generate
the expected output files which should be in the same location
and with the extension .markup replaced by .expected.
The test is also used as an installed test.
|
|
|
|
|
|
| |
Follow the prevailing practice and put the installed tests
into $libdir/installed-tests/$PACKAGE instead of
$pkglibdir/installed-tests.
|
| |
|
|
|
|
|
|
| |
If new test api is not available, do without it. In this
case, the tests won't work installed, but they should still
work uninstalled and in distcheck.
|
|
|
|
| |
This ensures that tests are run continuously on ostree.gnome.org.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Drop an unused variable, and don't call the deprecated
pango_cairo_font_map_create_context().
|
|
|
|
| |
ifdef out a function whose only use is already ifdef'ed out.
|
|
|
|
|
| |
This entire test is about the deprecated OpenType API.
Not much we can do except ignoring deprecations.
|
| |
|
|
|
|
|
| |
Valgrinding.... Apparently somewhere some memory corruption happens.
Argh...
|
| |
|
|
|
|
|
|
|
| |
Using 100 threads and 100 iterations per thread.
Only passes with fontconfig master. We will get a release made and
required soon...
|
|
|
|
|
| |
Can be run standalone now, compares the output of all threads and fails
if they mismatch.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Currently is not run automatically. But run it with args "10 100" and
see it crash...
|
|
|
|
|
|
| |
All tests in that file pass, lets keep it that way.
This is as of Unicode 6.1.0. 6.2 needs more work.
|