Skip to content

Add support for building libsigc++-3.0 with Meson #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 20, 2019

Conversation

kjellahl
Copy link
Contributor

This PR shows how libsigc++-3.0 (master branch) can be built with Meson instead
of Autotools. libsigc++-3.0 does not contain built source code, which simplifies
the meson.build files, compared to for instance libsigc++-2.0 and pangomm.

When building libsigc++-3.0 in maintainer-mode, the mm-common-get command must be
available, but M4 is not used.

I have copied meson.build files from pangomm and modified them.
docs/docs/manual/libsigc_manual.xml is converted to html files and a pdf file
in a way similar to what's done in gtkmm-documentation.

@fanc999 and other persons working with MSVC:

Can this be used for MSVC builds? Are modifications necessary?
Can MSVC build directly from git, now that M4 is not used?
M4 is used when building libsigc++-2.0 (libsigc++-2-10 branch) from git,
but it's not used when building libsigc++-3.0 (master branch) from git.

kjellahl and others added 4 commits December 10, 2019 13:10
libsigc++-3.0 can be built with either Autotools or Meson.
We need to make sure that SIGC_BUILD and _WINDLL are defined when
building the libsigc++ DLL, so that it gets build properly.
Instead of showing that 'mm-common-get' is not found, state that it is
required for maintainer-mode.
This avoids warnings and mis-compilations on certain system locales when
building on Visual Studio, in particular Chinese, Japanese and Korean
versions of Windows.
@kjellahl kjellahl merged commit 75119d0 into master Dec 20, 2019
@kjellahl kjellahl deleted the kjellahl/sigc3-meson branch December 20, 2019 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants