Issues for Qt5/KF5/KDE/CI system on OSX/MacPorts
Matthew Dawson
matthew at mjdsystems.ca
Tue May 27 04:51:02 UTC 2014
On May 27, 2014 07:53:03 AM Marko Käning wrote:
> On 27 May 2014, at 07:29 , Ben Cooksley <bcooksley at kde.org> wrote:
> > Please try the following syntax instead.
> > Note that I recommend you override this in
> > config/build/darwin-mavericks.cfg instead to ensure all CMake projects
> > on OS X are affected by it.
> >
> > configurePlatformArgs=-DCMAKE_INSTALL_BUNDLEDIR="{installPrefix}/Applicati
> > ons”
> Will do.
>
> > We're using /Applications within the install prefix here to ensure we
> > don't conflict with binaries, and also as they would normally be
> > separated on a normal system installation.
> >
> > As a note to the KConfig framework maintainer - I'm not sure about OS
> > X specifically, but I thought that /Applications was only supposed to
> > be used by full applications the user could run. kconfig_compiler
> > doesn't fit this….
>
> Hmm, I also don’t think this is the right place for it!
>
> I’d leave it in the SOME-PREFIX/lib/libexec/ path, if possible, if it is a
> tool only needed during installation…
>
> But, if this is not true and it is a tool for everyday-work on KDE, then I’d
> suggest something like /Applications/KF5/.
Speaking as the maintainer, I don't have any real experience dealing with OSX,
especially for development. I'm happy to have kconfig_compiler end up where
ever such tools are normally placed in OSX. I'll gladly follow any advice
but forward by the OSX experts in our community.
I'd consider kconfig_compiler a developer tool, similar to Google's protocol
buffer compiler. Where do such tools belong in the OSX world?
--
Matthew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3885 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140527/9fffcd2a/attachment.p7s>
More information about the Kde-frameworks-devel
mailing list