building 5.2/master branch with 5.1.2 installed?

[Kevin Funk]

On Wednesday, 6 September 2017 17:22:31 CEST René J.V. Bertin wrote:
> On Wednesday September 06 2017 16:55:17 Kevin Funk wrote:
> >We're talking about installing into the same prefix, right?
> >
> >Obviously that won't work as you'd be overwriting each others files. The
> >installation layout for the files installed by the 'embedded' kdevplatform
> >have not changed.
> 
> Evidently. That's only an issue from a packaging point of view, of course.
> 
> >In general: Different versions of KDevelop are not co-installable when put
> >in one prefix.
> 
> Again, it's not the installing itself that gives me pause, but whether or
> not I need to get rid of my current KDevelop install for building the 5.2
> branch (the "make" step, not the "make install" one). I could do that just
> to be sure, but I'm not expecting that the build will complete without
> issues in a single go which means I'd like to keep KDevelop around :)

I don't get the problem.

If you have a separate KDevelop install in e.g. /opt/kdevelop, then this won't 
interfere with the installation in e.g. /usr

You just need to make sure to properly set up things like CMAKE_PREFIX_PATH, 
{DY,}LD_LIBRARY_PATH, etc. pp., when building for the install in /opt/kdevelop 
so the build tools don't accidentally detect artifacts in /usr.

If installing into separate prefixes, with the correct env setup, there is no 
problem. I do this all the time.

Regards,
Kevin

> I could also just move $prefix/include/kdevplatform aside.
> 
> Cheers,
> René


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170906/e4bd8d3d/attachment-0001.sig>