kopete libgadu configure.in.in

Ralf Nolden nolden at kde.org
Sun Nov 16 10:08:05 GMT 2003


Hi,

can it be that you have to provide --with-libgadu-includes even if they are 
installed in standard path like /usr/include ? I think the configure.in.in 
there needs to have a ched for KDE_CHECK_HEADER on one of the gadu-includes 
instead of not providing a default location at all. Please correct me if I'm 
wrong :-)

Ralf
-- 
We're not a company, we just produce better code at less costs.
--------------------------------------------------------------------
Ralf Nolden
nolden at kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: signature
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20031116/22accc3b/attachment.sig>
-------------- next part --------------
_______________________________________________
Kopete-devel mailing list
Kopete-devel at kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel


More information about the kde-core-devel mailing list