On Tuesday 27 May 2014 17:30:56 Ben Cooksley wrote: > On Mon, May 26, 2014 at 9:04 PM, Alex Merry <alex.me...@kde.org> wrote: > > On Monday 26 May 2014 19:41:33 Ben Cooksley wrote: > >> On Mon, May 26, 2014 at 7:38 PM, <mk-li...@email.de> wrote: > >> > On 26 May 2014, at 09:35 , Ben Cooksley <bcooks...@kde.org> wrote: > >> >> For reasons stated above, application packages cannot reside within > >> >> /Applications. > >> >> If they need to reside within a separate directory, we'll need to > >> >> arrange this - however it needs to be within the installation prefix. > >> > > >> > Well, sure, I don’t want it now in /Applications for the CI system! > >> > How do we achieve installing it in the installation prefix then? > >> > >> You will need to wait for the CMake folks here to comment regarding > >> that i'm afraid. > >> As for /Applications, i'm assuming OS X doesn't give it any special > >> treatment... > > > > You need to pass > > -DCMAKE_INSTALL_BUNDLEDIR=some/relative/path > > to cmake. Possibly the default should change from an absolute path, I > > don't > > know, but we do want the defaults to be useful outside the CI system. > > Thanks for those details. I'm not sure what the defaults should be - > but I do agree that they should be usable outside the CI system. > Are there any other paths that OS X hardcodes which we should be wary of?
No, that's the only path that is absolute, and the only path that is special to OS X (all the other paths are the same on OS X as on other UNIX systems). Alex _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
