[gtkmm] Gtkmm-forge digest, Vol 1 #583 - 2 msgs

[gtkmm-forge-request lists sourceforge net]

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs.


Today's Topics:

   1. [Bug 129719] Changed - libgnomeprintmm-2.5.0 fails to build with older gcc (bugzilla-daemon widget gnome org)
   2. [Bug 129719] Changed - libgnomeprintmm-2.5.0 fails to build with older gcc (bugzilla-daemon widget gnome org)

--__--__--

Message: 1
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, dalgoda ix netcom com
Cc: 
Date: Sun, 21 Dec 2003 05:23:36 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 129719] Changed - libgnomeprintmm-2.5.0 fails to build with older gcc

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=129719

Changed by murrayc usa net 

--- shadow/129719	Sat Dec 20 01:39:53 2003
+++ shadow/129719.tmp.1030	Sun Dec 21 05:23:36 2003
@@ -58,6 +58,33 @@
 3) There also appears to be no entries in any Makefiles that would allow me
 to make my own local tweaks and have the build system automatically regen
 the files.
 
 Anyway, if the decision is made to not support older compilers, then it
 would be appropriate to add that as an autoconf feature test.
+
+------- Additional Comments From murrayc usa net  2003-12-21 05:23 -------
+> 2) Not sure where to find it.  I *think* I've installed every
+package > off
+> of gnome.org, though I may have missed whichever one has this tool. 
+> Pointers would be appreciated.
+
+gtkmmproc is part of gtkmm. You can read more about it in
+gtkmm/docs/internals/
+
+The code that you need to change is probably either in the .ccg file
+in libgnomeprintmm/libgnomeprint/src/, or in a .m4 file in
+libgnomeprintmm/tools/m4.
+
+It could be a generic enums conversion, but I think you would have
+seen that while building gtkmm itself.
+
+> There also appears to be no entries in any Makefiles that would
+>allow me
+>to make my own local tweaks and have the build system automatically regen
+> the files.
+
+Generated files should rebuild automatically when you change the
+source files. I'm not sure what you mean here. You _might_ need to
+configure with enable-maintainer-mode, which autogen.sh does
+automatically, which you must use when using cvs, which you should use
+to create patches.


--__--__--

Message: 2
From: bugzilla-daemon widget gnome org
To: gtkmm-forge lists sourceforge net, dalgoda ix netcom com
Cc: 
Date: Sun, 21 Dec 2003 14:39:59 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 129719] Changed - libgnomeprintmm-2.5.0 fails to build with older gcc

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=129719

Changed by dalgoda ix netcom com 

--- shadow/129719	Sun Dec 21 05:23:36 2003
+++ shadow/129719.tmp.29117	Sun Dec 21 14:39:59 2003
@@ -85,6 +85,31 @@
 
 Generated files should rebuild automatically when you change the
 source files. I'm not sure what you mean here. You _might_ need to
 configure with enable-maintainer-mode, which autogen.sh does
 automatically, which you must use when using cvs, which you should use
 to create patches.
+
+------- Additional Comments From dalgoda ix netcom com  2003-12-21 14:39 -------
+Ok... actually I've found out that it's no longer gtkmmproc but rather
+gmmproc and info located in glibmm/docs/internal, which explains why I
+couldn't find it.
+
+Joys of transitioning.  :->
+
+Still, since glibmm-2.3.x is out, I would have expected other
+GNOMEVER2.5 stuff to be using that one now.  Maybe still too early in
+the transition?
+
+Anyway, the corresponding .ccg file is pretty minimal; I saw nothing
+in there to obviously tweak.  And also, since I'm seeing this same
+issue in lots of other projects, I suspect it's really something that
+will have to be dealt with in the .m4 files.
+
+Still, I'm not sure I agree with your idea that regenerated files
+should not be rebuilt if the source file is touched.
+
+After all, imagine a project that using yacc/bison that ships with a
+pregenerated .c file.  If I modify the .y file, I expect the .c file
+to get updated.  I see similar things with IDL files in the Gnome
+project.  There is definite precedence for it and I think it would
+fall under "least surprise" to have the ability to regen them by default.



--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest