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

List:       kde-frameworks-devel
Subject:    Re: RFC Rules for installation of header files
From:       Kevin Ottens <ervin () kde ! org>
Date:       2013-11-15 16:52:31
Message-ID: 2180276.6pqGvkoBsb () wintermute
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Friday 15 November 2013 17:24:00 Aurélien Gâteau wrote:
> On Thu, 14 Nov 2013 17:55:42 +0100, Kevin Ottens wrote:
> > On Thursday 14 November 2013 18:40:04 Aurélien Gâteau wrote:
> >> Looks like we have an agreement then. Let me recap:
> >> 
> >> # Installation dir
> >> 
> >> All header files are installed in $PREFIX/include/KF5/$Framework.
> >> This includes 'k' prefixed headers like kfoo and KFoo,
> > 
> > I assume you meant kfoo.h here.
> > 
> >> non-prefixed headers such as bar.h and Bar, as well as special
> >> headers
> >> such as ${framework}_export.h and ${framework}_version.h.
> >> 
> >> # Include path
> >> 
> >> For 'k' prefixed headers, include path is
> >> $PREFIX/include/KF5/$Framework.
> >> 
> >> For non-prefixed headers, include path is $PREFIX/include/KF5.
> >> 
> >> Is this correct?
> > 
> > Looks correct to me.
> 
> David pointed out on IRC this scheme would need a significant change
> for
> frameworks like KIO or Solid: includes to <kio/foo.h> would need to be
> changed to <KIO/foo.h>, same with <solid/*> includes. Are you fine with
> this?

I am, but that looks like a big breakage in source compatibility though. :-)

Probably stupid idea: What about having kde4support install the compatibility 
headers for those?

Regards.
=2D- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com


["signature.asc" (application/pgp-signature)]

_______________________________________________
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel


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