| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Now that we're using new-style deprecations, we have to fight
a little harder to get rid of them inside pango.
|
|
|
|
|
|
|
| |
Update the copyright notice of this file, to reflect things more
accurately and to give more proper acknowledgement.
Please see: https://bugzilla.gnome.org/show_bug.cgi?id=767587#c16
|
|
|
|
|
|
|
|
|
|
| |
Add a configure check to see whether compiler directives are available
for exporting symbols, and use them if so. Likewise, update
the Visual Studio projects and config.h.win32.in to do likewise for
Windows builds.
We can then drop the .def files that were used to export symbols on
Windows builds, which should clean up things a bit.
|
|
|
|
|
| |
This is to ensure that we can override the verion macros to export the symbols
later.
|
|
|
|
|
|
|
| |
From the last commit, decorate all the symbols with the version
macros. Also add the version macros in the docs.
https://bugzilla.gnome.org/show_bug.cgi?id=767587
|
|
|
|
|
|
|
|
|
|
|
| |
This header is used for:
-Indicating what stable versions an API is introduced at and after 1.30.0.
-Indicating what APIs are deprecated, and which stable release series
they are deprecated if the deprecation is done after 1.30.0. This replaces
the use of G_DEPRECATED* in Pango.
-Use in a later commit to be used to export symbols directly via compiler
directives instead of doing so over .def files, for compilers that do not
support exporting via regex expressions.
|
|
|
|
|
| |
Allow the use of ${exec_prefix} for libdir and includedir when passing
them in as arguments to the script.
|
|
|
|
|
| |
Define HAVE_CAIRO_FREETYPE in the property sheets instead of disabling it
via conditional compilation, which makes things a bit neater.
|
|
|
|
|
| |
Cairo's headers could be in $(prefix)/include/cairo, so look for the
headers from there as well.
|
| |
|
|
|
|
|
|
| |
http://lists.w3.org/Archives/Public/www-style/2014Jun/0312.html
Thanks Lapo for pointing out this omission!
|
| |
|
|
|
|
|
|
| |
Since Pango coverage is initialized to PANGO_COVERAGE_NONE, it makes no
sense to perform calls to pango_coverage_set for characters that will
be set (or rather left) to none.
|
| |
|
|
|
|
|
|
|
| |
If python can be found at $(PythonPath)\python.exe (x86 builds) or
$(PythonPathX64)\python.exe (x64 builds), generate .pc files for Pango, as
appropriate with the build config chosen. This will make building
introspection on Visual Studio easier with packages that depend on Pango.
|
|
|
|
|
| |
This is used to generate the .pc files to make generating introspection
files easier for packages that depend on Pango.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This uses the newly-added autotools module so that the file list
for introspection using Visual Studio is now generated during
'make dist', along with the g-ir-scanner command line to generate
the .gir files and the compilation of the .typelib files.
This would help to simplify maintenance of the introspection
builds in Visual Studio, which is done using NMake.
https://bugzilla.gnome.org/show_bug.cgi?id=764984
|
|
|
|
|
|
|
|
|
|
| |
This adds a common autotools module that can be included in the
Makefile.am's so that we can get a list of sources and headers
that are to be introspected, as well as the complete g-ir-scanner
command(s) that are needed to generate the needed .gir's and
to compile the .typelib's.
https://bugzilla.gnome.org/show_bug.cgi?id=764984
|
| |
|
|
|
|
|
| |
This is a list of all the Emoji modifier bases and their
skin tone modifications.
|
| |
|
|
|
|
|
|
|
|
| |
Add finalizers to PangoWin32FontMap
Patch from Geoffrey Yerem.
Part of https://bugzilla.gnome.org/show_bug.cgi?id=764089
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=764191
|
| |
|
|
|
|
|
| |
Unicode says: "U+1680 ogham space mark is unusual in that it is generally
rendered with a visible horizontal line, rather than being blank."
|
|
|
|
| |
We ought to include the platform-neutral headers first...
|
|
|
|
|
| |
It was referring to itself for further description, but I assume the
intent was to refer to pango_layout_line_x_to_index().
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This brings us back in sync with GUnicodeScript.
|
|
|
|
| |
No changes here.
|
| |
|
|
|
|
|
|
|
|
|
| |
This partially reverts 03e60dc.
As we now ensure that items using GResources and GConstructors are always
referenced so that the linker does not optimize them out in a default
Release build, we no longer need to enforce the use of /LTCG, so
/LTCG:incremental will work as well.
|
|
|
|
|
|
|
|
|
| |
MSVC 2015 changed its default link-time code generation setting to
/LTCG:incremental, which causes problems if /opt:noref is to be used,
meaning that some code will be optimized out by the linker.
Avoid this situtation here by enforcing the use of /LTCG for MSVC 2010+
builds.
|
| |
|
| |
|
|
|
|
| |
...except for the .sln and the README.txt files, to ease maintainenance.
|
|
|
|
|
|
| |
Fix the projects, and consolidate repeated items into the property sheets,
as they now need to compile and link against HarfBuzz. Also remove
unnecessary lines from the PangoFT2 and PangoCairo project files.
|
|
|
|
| |
Remove unneeded AdditionalIncludeDirectories directive.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
Pango uses the HB_VERSION_ATLEAST macro, but it was only
defined in HarfBuzz 0.9.30. Thus, compiling with an older
version fails.
Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh>
https://bugzilla.gnome.org/show_bug.cgi?id=756015
|
|
|
|
|
|
|
|
| |
Update the notes that this is also used for Visual Studio 2015 support,
and correct the MSVC_VER_LONG for MSVC 2015, which is 14, not 2015.
Also add a note that this can be used for other projects that have
Visual Studio build support.
|
|
|
|
|
| |
Handle also the situation where $(srcdir) == $(top_srcdir), so that this
can also be used in cases like librsvg and gobject-introspection.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Avoid determining the Unicode type repeatedly. Instead,
just get the type once and filter out the classes we want.
|