Re: Compiling and options
- From: Murray Cumming <murrayc murrayc com>
- To: "D. B." <db0451 gmail com>, Russel Winder <russel winder org uk>, gtkmm-list gnome org
- Subject: Re: Compiling and options
- Date: Mon, 18 Apr 2016 15:06:27 +0200
On Mon, 2016-04-18 at 13:51 +0100, D. B. wrote:
Russel: Just reorder arguments in your makefile such that your own
compiler options come after pkg-config's ones. Any later value for a
given option overrides the earlier one.
Murray: I had to do exactly this to use -std=c++14 on Debian testing,
so yes, it does happen 'in the wild'.
I can't find any such patch for the debian packages via this system:
https://sources.debian.net/patches/gtkmm3.0/
https://sources.debian.net/patches/glibmm2.4/
Please show us the output of these commands, so we can see exactly
where this -std=c++11 is coming from:
$ pkg-config glibmm-2.4 --cflags
$ pkg-config gtkmm-3.0 --cflags
Do you mean that 'plain' gtkmm does not enforce any -std?
Indeed. It does not, for this very reason.
I thought C++11 was required for gtkmm, but do you normally require
users to add that manually in their own place?
Yes. Adding it as CFLAG from pkg-config would cause this very problem.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]