Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
See libsigcplusplus PR#83
|
|
See gtkmm#131
|
|
It's deprecated from Meson 0.64. The replacement, fs.copyfile(),
is not useful here. It only copies from the source directory to
the build directory.
|
|
See https://gitlab.gnome.org/GNOME/gtkmm/-/merge_requests/72 (William Roy)
|
|
and require cairo >= 1.14.0
|
|
Add a short description for the warning-related compiler flags for Visual
Studio.
Also, use the `/wd4267` compiler flag only when building a 64-bit build, since
warning C4267 only applies for 64-bit builds.
|
|
Since cairomm does not hard-depend on GLib, it may be the case that
msvc_recommended_pragmas.h is not available during the build. If it is not,
disable warnings C4244 and C4101, which are part of the warnings that it
disables.
|
|
|
|
The default value will be changed in future Meson releases.
Don't use deprecated python3.path() and execute(..., gui_app: ...).
Don't distribute .gitlab-ci.yml.
|
|
Make these builds distinct from the Visual Studio 2019 builds.
|
|
New versions of mm-common use the Python scripts doc_postprocess.py
and doc_install.py instead of the Perl scripts doc-postprocess.pl and
doc-install.pl when documentation is built.
|
|
Doxygen in a main project shall not be called before tag files have been
created or updated in subprojects.
|
|
* meson.build: If mm-common-get is not found in maintainer-mode
with 'required: false', try with 'required: true'.
Don't try to use tag_file, if documentation is not built.
* docs/reference/meson.build: Don't use variables from modules
that don't define doxytagfile. These are subprojects that don't build
their documentation.
|
|
We can now drop the ignores for warnings C4251, C4273 and C4275 along with
C4530, since our code and compiler flags should now make us free of them,
since we use /EHsc to build our code and we are clean of classes that we
export as a whole that derives from std::xxx classes.
Ignore warning C4800, and warning C4127 in the examples, since these warnings
are really spurious and safe to ignore as a whole.
|
|
* meson.build:
* docs/reference/meson.build:
Call add_dist_script() in a subproject, if meson.version() >= 0.58.0.
|
|
cairo and sigc++ can be subprojects of cairomm.
|
|
Scripts that simplify releasing new versions of cairomm.
|
|
|
|
See https://github.com/libsigcplusplus/libsigcplusplus/pull/65
|
|
Has been a requirement for a long time, but configure.ac
and meson.build had not been updated.
|
|
|
|
This makes the built DLL and .lib's contain the toolset version if
the build is carried out using Visual Studio 2017 or later, unless
the 'msvc14x-parallel-installable' option is set to be false during
configuration.
The reasoning behind this change is that there may be subtle problems
when, for instance, one tries to link to a Visual Studio 2017-built
cairomm with Visual Studio 2019. This is unfortunate as Microsoft
did try hard to make interoperating between binaries built with Visual
Studio 2017 and 2019 as easy as possible in terms of ABI and API, but
unfortunately this may hit the corner cases where this compatibility
does not work.
As the name suggests, this attempts to make Visual Studio 2017
and 2019 builds share a single set of underlying C DLLs easier,
while avoiding possible breakages caused by such subtle differences.
|
|
Instead, we use the newly-added CAIROMM_API which is defined to be
__declspec(dllexport) to export the symbols directly.
This will also allow some cleanup in the Meson build files, as we do not
need to differentiate how the cairomm library is built on different
compilers.
|
|
Turn on the -Wzero-as-null-pointer-constant warning when -Dwarnings=max
or fatal. Replace 0 by nullptr where appropriate.
|
|
This adds an option to the Meson builds so that we can choose to use a
shared build of Boost::Test if needed.
|
|
Cairo could have been built with FreeType support but has no FontConfig
support, so we need to check for that too.
Also allow building the tests on Windows even if FontConfig is not
found, as a result.
|
|
We only put Cairo as a required package if Cairo was found via pkg-config, but
if Cairo was found manually, we make the pkg-config file link to the cairo
library directly (-lcairo).
|
|
Visual Studio and some MinGW versions require defining this to use M_PI
|
|
The Visual Studio build files for Cairo do not generate pkg-config files for
us, so we need to look for the cairo library and the header files. Since we
are doing this for Visual Studio builds only, we want to look for both cairo.h
and cairo-win32.h.
|
|
cairomm can be built with either Autotools or Meson.
Fixes #20
|