Re: [sigc] 1.2.5 and Win32 (multiple compilers)

[Ulrich Eckhardt <eckhardt satorlaser com>]

Asko Kauppi wrote:
> I'm making a multi-OS, multicompiler framework for building ParaGUI
> applications.  On Win32 and WinCE systems, I leverage the libSigC++
> sources with the framework, and they are compiled into it
> automatically.

Just wondering, didn't the Paraguys want to incorporate libsigc++ into ParaGUI 
itself? I know that I once sent them a patch that used boost::function as a 
replacement for C-style callbacks and void pointers, but that was refused due 
to the plan to use libsigc++ and (IMHO) FUD about templates and code-bloat.

> - Can the build-generated header files (bind.h, bind_return.h,
> class_slot.h, hide.h, method_slot.h, object_slot.h, retype.h,
> retype_return.h, signal.h, slot.h) be the same for all of these
> compilers, that is, can I do all the customization in 'sigcconfig.h'?

Those files are generated with m4, which, being a text-oriented tool, emits 
platform independent code.

> - How should I configure eVC++ in the 'sigcconfig.h' file, since it's
> not necessarily equal to either VC++ 6.0 or .NET in its capabilities?

Try and error, there are unittests you can compile and run to make sure things 
work as expected.

good luck

Uli