Copy and update the relevant items in the visual Studio 2010 projects
so that we have project files that is usable out-of-the-box in Visual
Studio 2019, like what we did for the Visual Studio 2012~2017
projects.

Use the HIGHENTROPYVA linker option on x64 builds with MSVC 2012 and
later to enhance the security of the built binaries.

Pointed out by Ignacio Casal Quinteiro.

Some files that this script will process might have UTF-8 items in
there, which can cause problems on Python 3.x as it is more strict and
careful on unicode issues.  Fix this by:

-Doing what we did before on Python 2.x
-Opening the file with encoding='utf-8' on Python 3.x

This fixes a possible out of bound when reading rgbs which
are longer than the support MAXLONG

When reading bytes we weren't check that the index wasn't
out of bound and this could produce an invalid read which
could deal to a security bug.

Mattia Rizzolo authored Jan 03, 2017 and Ignacio Casal Quinteiro committed Mar 26, 2017

Signed-off-by: Mattia Rizzolo <mattia@debian.org>

https://bugzilla.gnome.org/show_bug.cgi?id=776798

Mattia Rizzolo authored Jan 03, 2017 and Ignacio Casal Quinteiro committed Mar 26, 2017

https://bugzilla.gnome.org/show_bug.cgi?id=776798

Mattia Rizzolo authored Jan 03, 2017 and Ignacio Casal Quinteiro committed Mar 26, 2017

https://bugzilla.gnome.org/show_bug.cgi?id=776798

Generate and copy the libcroco-0.6.pc during the "install" stage of the
build, when a Python installation is found at the configured location in
croco-version-paths.[vsprops|props].

Also fix the 201x "install" project as a "'" is missed, and clean up
things a bit.

This adds Python scripts to generate .pc files for libcroco, so that
it is easier for people who need to use the .pc files for the package.
Integration to generate the .pc files will be added later to the project
files.

Update croco-version-paths.[vsprops|props].in to record the major, minor
and micro versions of a release, and assemble the API version from these
values.  This prepares for generating the .pc file for libcroco.

We need to bump the micro version here as well...

This enables us to go one less layer down the tree to reach the projects and
allows the autotools modules Makefile-newvs.am and Makefile.msvcproj be in
sync with the latest ones in GLib master.

This updates the autotools scripts so that we can support Visual Studio 2017
by copying the 2010 projects and update items in there as needed.

Note that the format of the toolset version string changed for Visual Studio
2017, so allow a custom toolset version string to be passed in and used,
otherwise the platform toolset string is generated as before.

Note also that Visual Studio 2017 aims to be compatible with 2015 on the
CRT level, so one should be able to use 2017-built binaries with 2015-built
binaries without problems.

This is to ensure the changes in the generated
build/win32/vs10/croco-install.props are applied in
build/win32/vs[11|12|14] as well.

Make the Makefile.am targets for generating the Visual Studio projects re-generate the
project files and the header listings whenever the Makefile.am's that include
build/Makefile.msvcproj changes, so that whenever a source/header is added, they will
be reflected in the projects and in the property sheets that are used to copy the
headers.

Also ensure that these are applied to the vs11, vs12 and vs14 projects when this
happens, as they are copied and processed from the Visual Studio 2010 projects.

Order the search sequence of the headers to conform better to the
dependency hierarchy.

Commit bc9b2c33 introduced an intermediate variable to account
for the difference in signedness between cr_tknzr_consume_chars()
and cr_input_consume_chars(), but missed that the variable in
question is an in-out variable that requires proper initialization.

https://bugzilla.gnome.org/show_bug.cgi?id=759565

Logical ! was only applied to the left side of the comparison

https://bugzilla.gnome.org/show_bug.cgi?id=758394

https://bugzilla.gnome.org/show_bug.cgi?id=710076

* Add an end label to go to on error
* Clean up xml_doc at the end
* Fix a miscleaning of xpath_object
* Unref sheets after they are given to a cascade
* Return status at the end

https://bugzilla.gnome.org/show_bug.cgi?id=710076

* Return status

https://bugzilla.gnome.org/show_bug.cgi?id=710076

* Don't set status to CR_OK, it's initialized to that value
* Return status

https://bugzilla.gnome.org/show_bug.cgi?id=710076

* Return status instead (initialized to CR_OK) instead of an explicit CR_OK
* Remove redundant check for *a_in_len < 1 (equivalent to *a_in_len == 0)
  and remove now-unused end label

https://bugzilla.gnome.org/show_bug.cgi?id=710076

https://bugzilla.gnome.org/show_bug.cgi?id=710076

https://bugzilla.gnome.org/show_bug.cgi?id=710076

https://bugzilla.gnome.org/show_bug.cgi?id=710076

https://bugzilla.gnome.org/show_bug.cgi?id=710076

https://bugzilla.gnome.org/show_bug.cgi?id=726993

TYPE_SELECTOR equals to 2, so condition
(cur_sel->type_mask | TYPE_SELECTOR) will always be true. We should
increase c only if we encounter a selector.

Issue detected by Cppcheck and MSVS (see
https://bugzilla.gnome.org/show_bug.cgi?id=507484

)

Signed-off-by: Boris Egorov <egorov@linux.com>