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'. Do you mean th
ality. :-)
Cheers
On Mon, Apr 18, 2016 at 2:06 PM, Murray Cumming 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 valu
Thanks, both! So it wasn't my other package causing it, at least :-) If
nothing else, it's news to me that people seemingly expect GCC 6 to hit
Debian testing soon... We'll see how well that works out.
For now, I'll keep hacking around their hack! Maybe add some grumblings to
their bugtracker late
Hello,
I encountered the same thing when writing an internal library used to
collect some pre-main-program config from users. I couldn't just make this
concurrent with my main window (hidden until required) since it's reusable
code. As you've suggested, I just gave the initial config window its ow
Given that TreeValueProxy uses a conversion operator returning a const
value of the template type, you simply need to tell the compiler to use
that conversion operator, so that it doesn't try to invoke .first on the
TreeValueProxy class itself.
You should be able to simplify the existing suggestio
Not to stand in the way of other users who might have valid logistical
barriers to that - but fwiw, I don't and would be very enthusiastically in
favour of requiring -std=c++14
The appeal of gtkmm to me is its cutting-edge adoption of modern C++
standards and recommended techniques, especially whe
I had this before. Based on research I think it might be caused by not
compiling in GUI mode, i.e. with* -mwindows* switch etc.
IIRC I could then start it from a cmd prompt - to ensure I'd see any
stdout/err - which wouldn't open the 2nd window like before, nor give the
error
Although I changed
Btw, make sure you're using the mingw64 shell to compile, NOT the msys2
one! The latter should only be used for downloading/updating packages and
etc.
On Tue, Aug 16, 2016 at 1:05 PM, D. B. wrote:
> I had this before. Based on research I think it might be caused by not
> compiling
Although this isn't actually a gtkmm issue, or even a GTK+ one - rather
GLib/GObject as the message shows - did anyone ever figure out a reliable
explanation as to why it happens and how to prevent it?
-mwindows as I suggested is not working on my current example, oddly.
__
Since AFAICT, somehow no one else had done it yet I've opened a bug
report for this here:
___
gtkmm-list mailing list
gtkmm-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtkmm-list
curse my keyboard. here's the missing bit
On Thu, Aug 25, 2016 at 2:42 PM, D. B. wrote:
> Since AFAICT, somehow no one else had done it yet I've opened a bug
> report for this here:
>
>
https://bugzilla.gnome.org/show_bug.cgi?id=770392
___
Heh, it HAD been reported, but Bugzilla search didn't find a match as I was
writing up my title, probably because mine was too specific...
Here we go:
https://bugzilla.gnome.org/show_bug.cgi?id=769076
...and there are patches there, though I can't see any indication that a
fix has been committed y
On Sat, Sep 10, 2016 at 1:00 PM, wrote:
>
> I need to add the following functions:
>
> virtual Gtk::SizeRequestMode get_request_mode_vfunc() const;
> virtual void get_preferred_width_vfunc(int& minimum_width, int&
> natural_width) const;
> virtual void get_preferred_height_for_width_vfunc(int wid
I noticed this in Builder, but it applies equally to DevHelp in the main
(which Builder just calls on).
Both the gtkmm and glibmm documentation sets are shown as options in
DevHelp, but they're unusable. DevHelp gives an "Error opening the
requested link" on the 1st try to open any document in eit
On Mon, Sep 19, 2016 at 8:29 PM, Phil Wolff wrote:
> My system: Ubuntu 16.04, libgtkmm-3.0-doc 3.18.0-1, libglibmm-2.4-doc
> 2.46.3-1, devhelp 3.18.1. Docs are accessible via devhelp as expected.
>
> I note that the two links you specify were reported in 2011 and 2007…
>
For all I know, they're
Personally I just installed MSYS2 and used its own precompled 32 and 64 bit
packages of GTK+/gtkmm/etc without problems. Then just keep running your
exe until you figure out all the DLLs that you need to distribute in the
same folder with it.
___
gtkmm-li
FYI, it looks like some kind of space character in your original email has
been changed to a question mark symbol throughout, which makes it hard to
read, at least here on GMail. Maybe you could reconfigure your email at the
sending side to avoid this. Hope this helps!
_
>
> One question: does using MSYS2 to generate the binaries generate a
> dependency on Cygwin library (dll)? If yes, that does not fit the purpose
> of having a native Windows environment.
Of course it doesn't fit, and that's why it doesn't happen! MSYS2 also
provides mingw-w32 and -w64 shells wi
On Sat, Dec 31, 2016 at 12:00 PM, wrote:
>
> Message: 1
> Date: Fri, 30 Dec 2016 13:36:20 +0100
> From: Kjell Ahlstedt
> To: Pavlo Solntsev
> Cc: gtkmm-list@gnome.org
> Subject: Re: gtkmm compilation issue via jhbuild
> Message-ID: <2f3d927f-77f6-02bd-ef5e-94f09a7b3...@bredband.net>
> Content-T
OP, I've created a Bugzilla for you:
https://bugzilla.gnome.org/show_bug.cgi?id=776658
___
gtkmm-list mailing list
gtkmm-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtkmm-list
On Sun, Jan 1, 2017 at 12:00 PM, wrote:
>
> Date: Sat, 31 Dec 2016 22:59:15 -0600
> From: Pavlo Solntsev
> To: gtkmm-list@gnome.org
> Subject: Re: gtkmm compilation issue via jhbuild
> Message-ID: <1483246755.3065.8.ca...@meta.ua>
> Content-Type: text/plain; charset="UTF-8"
>
> Thank you, D.B.
>
On Fri, Jan 20, 2017 at 12:00 PM, wrote:
> Date: Fri, 20 Jan 2017 12:25:48 +0530
> From: Amit
> To: gtkmm-list@gnome.org
> Subject: Gtkmm GUI fails to update
>
> [...]
>
> Window A has button called Dialogwindow A which invoked a
> Dialogwindow and shows .
>
> Window B has separate Thread
On Sat, Jan 21, 2017 at 12:00 PM, wrote:
> Date: Fri, 20 Jan 2017 15:27:49 -0500
> From: Damon Register
> To:
> Subject: Re: EXTERNAL: ANNOUNCE: gtkmm 3.89.3
> Message-ID: <69919c63-22ce-1d61-ada0-2c0fb6e8f...@lmco.com>
> Content-Type: text/plain; charset="utf-8"; format=flowed
>
> On 1/20/2017
On Sun, Jan 22, 2017 at 12:00 PM, wrote:
>
> Date: Sat, 21 Jan 2017 10:10:09 -0500
> From: Bill William
> To: gtkmm-list@gnome.org
> Subject: msys2 DLL out of date error with libgtksourceviewm-3.0.0.dll
> Message-ID:
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I wanted
On Mon, Jan 23, 2017 at 12:00 PM, wrote:
>
> Date: Mon, 23 Jan 2017 06:37:15 -0500
> From: Damon Register
> To:
> Subject: Re: EXTERNAL: ANNOUNCE: gtkmm 3.89.3
> Message-ID:
> Content-Type: text/plain; charset="windows-1252"; format=flowed
>
> On 1/21/2
tent-Type: text/plain; charset="windows-1252"; Format="flowed"
>
>
> Hi D. B .
>
> [...]
> *does it handle all calls to GTK++/mm functions?*
>
> Pls Clarify ...
>
I think I must've been thinking of something different. By reading
https://develop
On Mon, Jan 23, 2017 at 1:48 PM, D. B. wrote:
>
>> The second item was a really ugly oversized theme that I was not
>> able to change. This is the one that made it useless for anything
>> that I wanted to do. I did some hunting for a solution but the
>> only thing I
27 matches
Mail list logo
