Re: libtool-2 problem: Building a QT3 Designer plugin

[Tim]

Ah, sorry, I always thought -lrt stood for the c runtime library 
which I thought was responsible for the main() requirement.

It IS attempting to link a program rather than a library.
We have the line: 
inst_PROGRAMS = musewidgetsplugin.so

I assumed that this was the only way the original author
 could get it to build a single .so
He has some commented-out attempts at making it
 an LT lib instead. I assumed that didn't give him
 the results he wanted, and as I mentioned, when I 
 attempted the same thing, I got an .so, .la and .a
 but they didn't work.

I can remove this feature and probably should,
 since who's gonna use widgets for QT3 in a new 
 project anyway...

But now I'm just really curious as to what is the proper way
 to make this work, in case I run into this again.
Seems a bit of a unique case? I mean none of the other
 QT3 Designer plugins also have .la or .a files or even
 version numbers appended to their .so  

I read the QT3 docs but they only describe how to
 build plugins using QT3 programs and don't mention
 using libtool.

Thanks. Tim.


On Friday 06 November 2009 09:58:10 am you wrote:
> On Thu, 5 Nov 2009, Tim wrote:
> > libtool-2, however, insists on linking the runtime
> > library (-lrt) with the .so, hence we get an
> > error that main() is not found in the .so
>
> I am not sure what OS you are using but on most systems -lrt brings in
> the library for the POSIX .4 Real Time extensions ("rt" == "Real
> Time").  This is needed for things like POSIX message queues, POSIX
> memory mapping, and nanosleep().  Using this library should not impose
> a requirement for main() in a shared library.  A requirement for
> main() would imply that libtool was attempting to link a program
> rather than a library.
>
> Bob
> --
> Bob Friesenhahn
> address@hidden, http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/