RE: [gtkmm] build problems with 1.2.10 (gcc 2.95.3)

[Murray Cumming Comneon com]

Murray Cumming
murrayc usa net
www.murrayc.com 

> -----Original Message-----
> From: zsh perilith com [mailto:zsh perilith com] 
> Sent: Mittwoch, 19. März 2003 12:19
> To: gtkmm-list gnome org
> Subject: [gtkmm] build problems with 1.2.10 (gcc 2.95.3)
> 
> 
> Salutations,
> 
> with gtkmm 1.2.10 and gcc 2.95.3 i get this build crash: 
> 
> In file included from wrap.cc:1:
> ../gtk--/object.h:3: unterminated string or character constant
> ../gtk--/object.h:4: unterminated string or character 
> constant In file included from wrap.cc:1:
> ../gtk--/object.h:291: unbalanced `#endif'
> gmake[4]: *** [wrap.lo] Error 1
> [... etc etc ...]
> 
> which seems to be due to:
> 
> #ifndef _`'_UPPER_(translit(`gtkmm_object', `-', `_'))`'_H 
> #define _`'_UPPER_(translit(`gtkmm_object', `-', `_'))`'_H

These look like fragments of unparsed m4.

> in object.h, two lines which are fully indeciferable (does ` 
> even have special meaning in C/C++?)

There are lots of those characters in the m4 code.

> Since this file is generated by gtkmmproc my first guess was 
> install GNU m4 (im on OpenBSD 3.3)

Did you have a different m4?

I remember also that gnu make might be a requirement for gtkmm 1.2.

>, but that didnt help. So I 
> just replaced them with #ifndef _UNIQUE_STRING_ etc. It built 
> fine.

I suggest you just concentrate on the m4 parsing problem.

However, this _UNIQUE_STRING_ thing is interesting. Is that standard, or a
gcc extension? Can you give us an informative URL telling us about that?

> Then, when trying to build the software that depended 
> on gtkmm, I found this same wacked-out #ifndef was at the top 
> of each header, so I wrote a perl script to replace that with 
> unique strings and voila. Whats up with this stuff? Are all 
> you gtk people just on drugs or what? Is my gtkmm somehow 
> broken without this magic sequence? Should I just give up and 
> use debian?!?
> 
> I eagerly await your response.
> 
> (I was also very intrigued by the --enable-voodoo in the 
> configure script, you silly gtkmm coders!)

Unless you specifically need gtkmm 1.2 for a particular application, I do
suggest you start your experiences with gtkmm 2. For a start, we distribute
generated files to avoid these kinds of problems.