running different version from its build directory?
kfunk at kde.org
Sat Sep 28 10:56:44 BST 2019
On Saturday, 28 September 2019 11:15:42 CEST René J.V. Bertin wrote:
> 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)?
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 . Could be
be fixed by adding some more CMake logic, but that needs to be implemented &
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.
> 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.
 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...
Size: 195 bytes
Desc: This is a digitally signed message part.
More information about the KDevelop-devel