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

List:       kde-pim
Subject:    Re: [Kde-pim] Using KDE_EXPORT
From:       David Faure <dfaure () klaralvdalens-datakonsult ! se>
Date:       2005-03-01 17:21:23
Message-ID: 200503011821.24673.dfaure () klaralvdalens-datakonsult ! se
[Download RAW message or body]

On Tuesday 01 March 2005 18:08, Allen Winter wrote:
> So, in summary, we should have LIBxxx_EXPORT on all public classes in all our libraries?
Yes. Shared libraries to be precise (see below).

> For example,  in libemailfunctions we should have LIBEMAILFUNCTIONS_EXPORT,
Errr bad example..... libemailfunctions isn't a real shared lib, it's just a convenience library
(see the Makefile.am howto for the distinction).
So there's no problem for that one, unless there are apps which use those functions
*via* libkdepim, without linking to libemailfunctions directly... but I doubt it.

> where #define LIBEMAILFUNCTIONS_EXPORT KDE_EXPORT??
Yes (by default - set those#defines in a central place, like a kdepim_export.h,
for consistency with kdelibs_export.h and koffice_export.h)

-- 
David Faure -- faure@kde.org, dfaure@klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/

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