I guess you have already noticed that your error messages come from the
typedefs in code sections such as this one:
#ifdef SIGC_TYPEDEF_REDEFINE_ALLOWED
/** This typedef is only for backwards-compatibility.
* It is not available when using the SUN Forte compiler.
* @deprecated slot_list_type;
*/
typedef slot_list_type slot_list;
#endif
This code was deleted 2007-08-14, and it does not exist in libsigc++
version 2.1.1 and later. You seem to have very old code.
You can try to do as recommended in comments near the beginning of
signal.h, i.e. comment out
#define SIGC_TYPEDEF_REDEFINE_ALLOWED 1
I don't guarantee that it will solve your problems, but it's worth trying.
//SIGC_TYPEDEF_REDEFINE_ALLOWED:
// TODO: This should have its own test, but I can not create one that
gives the error instead of just a warning. murrayc.
// I have just used this because there is a correlation between these
two problems.
#ifdef SIGC_TEMPLATE_SPECIALIZATION_OPERATOR_OVERLOAD
//Compilers, such as older versions of SUN Forte C++, that do not
allow this also often
//do not allow a typedef to have the same name as a class in the
typedef's definition.
//For Sun Forte CC 5.7 (SUN Workshop 10), comment this out to fix the
build.
#define SIGC_TYPEDEF_REDEFINE_ALLOWED 1
#endif
You sent your email 6 days ago, and I received it just a few hours ago.
Is that because you are not a member of libsigc-list? If you don't want
to become a member, but still want to continue this discussion, I will
get your messages much faster if you send them both to me and to the list.
Kjell
2012-01-11 10:40, da Eatel skrev:
Don´t know how to do it most correctly so I tried to attach my
signal.h to e-mail (its copy is on pastebin.com/t2fGNhsp
<http://pastebin.com/t2fGNhsp> ). I compared it with signal.h file I
ams using for Unix and it´s a lot different. My signal.h file for
Windows comes from Gtk+ or Gtkmm package downloaded from GTK website.
Dne 9.1.2012 15:35, Kjell Ahlstedt napsal(a):
I haven't got mingw installed, and I have never used it, so I'm not
the best person to reply.
When I compare your error messages with my file sigc++/signal.h, it
does not seem to fit at all. Lines 1675, 1784, and 1895 are not even
close to anything that might produce your error messages. (I'm
running Ubuntu 11.10, and I've fetched libsigc++ from the git
repository, and built it locally.)
If you can attach your signal.h file, I can try to understand what's
wrong.
Do you use the same signal.h when you compile for Linux, and succeed?
If you do, then I suppose there's nothing wrong with the header file,
and I will probably not find anything that can explain your error
messages.
Kjell
_______________________________________________
libsigc-list mailing list
libsigc-list@gnome.org
http://mail.gnome.org/mailman/listinfo/libsigc-list
