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

List:       kde-core-devel
Subject:    Re: Writing KParts plugins
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-07-02 10:11:33
[Download RAW message or body]

On Sun, Jul 02, 2000 at 12:37:36AM -0400, Dawit Alemayehu wrote:
> On Sat, 01 Jul 2000, David Faure wrote:
> > On Sun, Jul 02, 2000 at 01:19:50AM +0100, Richard Moore wrote:
> > > file:/home/rich/src/writing-plugins/writing-plugins.html
> > > 
> > > I've written a tutorial based on the plugin I wrote this evening.
> > > Could someone check it for errors before I stick it on the developer
> > > site?
> > 
> > Great that you wrote that ! Excellent.
> > 
> > Just one comment (after reading HTML as plain text, so I didn't really
> > read the code): I think you should use $(KDE_PLUGIN) in the LDFLAGS line.
> > The word plugin means something slightly different here, but it applies
> > to KParts plugins as well :-)
> > 
> > I'm glad you found it easy to figure out :-)
> > (That was priority number 1 when designing KParts ;)
> 
> Hmmm... is this because of all the DSO unloading stuff we do now ?  I was just
> curious about the reason why it would need to be $(KDE_PLUGIN) compared to
> $(all_libraries).

grep KDE_PLUGIN Makefile
KDE_PLUGIN = -avoid-version -module -no-undefined

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today
See http://www.kde.org/kde1-and-kde2.html for how to set up KDE 2

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