running different version from its build directory?

[Kevin Funk]

On Saturday, 28 September 2019 11:15:42 CEST René J.V. Bertin wrote:
> Hi,
> 
> I'm looking for suggestions/best-practices on how to do safe test runs of a
> newer KDevelop version from its build directory or else a "destroot" (e.g.
> 5.4.3 with 5.3.2 installed)?

Heya,

Running from the build directory is not easily doable; as the libs + plugins 
built by KDevelop are not being placed in a common sub-directory [1]. Could be 
be fixed by adding some more CMake logic, but that needs to be implemented & 
tested, etc..

I'm not sure what's the problem with the traditional way of installing 
KDevelop into a separate prefix (-> -DCMAKE_INSTALL_PREFIX=...), setting up 
PATH/QT_PLUGIN_PATH/LD_LIBRARY_PATH (or DYLD_LIBRARY_PATH on macOS) and 
running the specific kdevelop binary then? That always worked fine.

Also see:
  https://community.kde.org/KDevelop/HowToCompile_v5#3._Run_KDevelop

Regards,
Kevin

> I guess I could make an AppImage but I have no idea what the associated
> learning curve and overhead are.

As you indicated, that's overkill. There's a much simpler solution.

> Thanks,
> R.

[1] Hint: https://cmake.org/cmake/help/v3.12/prop_tgt/
RUNTIME_OUTPUT_DIRECTORY.html & friends

-- 
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: 195 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20190928/749332be/attachment.sig>