[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: klibfactory cleanup
From:       Harri Porten <porten () trolltech ! com>
Date:       2001-09-24 14:14:35
[Download RAW message or body]

On Mon, 24 Sep 2001, Simon Hausmann wrote:

> > #define KDE_EXPORT_COMPONENT_FACTORY( factory ) \
> >    extern "C" void *kde_init#factory() { return new factory; }
> > 
> > ?
> 
> And how do you find out the kde_init<Factory> symbol name when all you know
> is the dsoname? :-} (factory argument can be "MyFoo" while the libname is
> "libblah", where only the latter you know from the dlopen'ing side)

Then let the export macro have two arguments.

> Do I understand things correctly that it comes down to the question if
> we want to be able to statically link components and if we want to run
> on platforms unsupported by Qt? ;-)

AFAIK Designer only works on Windows with a static built I'd be careful
to use the word "supported" as this would leave 0 platforms for KDE ;)

Seriously: the main reason why I'd be against a unique symbol name is the
limitation to one factory per library. But if that's not so much of an
issue I wouldn't care so much.

Harri.

[prev in list] [next in list] [prev in thread] [next in thread]