Re: Compiling and options

["D. B." <db0451 gmail com>]

Hi Murray,

Thanks for the fast explanation! Makes sense. And of course, I'll try these out later and let you know.

This might just be the usual problem of me being really forgetful - I just remembered I'm querying another package at the same time (as my current makefile only manages 1 set of options for all object files). I'll double-check and get back to you. I expect you're completely correct, of course, and PEBKAC. Or at least, the other package isn't as careful to preserve users' chosen settings as gtkmm thankfully is - another example of its excellent quality. :-)

Cheers

On Mon, Apr 18, 2016 at 2:06 PM, Murray Cumming <murrayc murrayc com> wrote:

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