@rolandlo @bhennion, we should add something like this to the CMake scripts, to ensure that everyone uses the installation:

[Febbe]

          @rolandlo @bhennion, we should add something like this to the CMake scripts, to ensure that everyone uses the installation:

if(CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
    set(CMAKE_INSTALL_PREFIX "${CMAKE_BINARY_DIR}/install" CACHE PATH "Default install path." FORCE)
    set_target_properties(xournalpp PROPERTIES RUNTIME_OUTPUT_DIRECTORY "${CMAKE_BINARY_DIR}/install/bin")
endif()

add_custom_command(
    TARGET xournalpp POST_BUILD
    COMMAND ${CMAKE_COMMAND} --install ${CMAKE_BINARY_DIR} --config $<CONFIG>
)

This will automatically install Xournal++ into <build>/install/bin.
It also integrates with build tools, since the RUNTIME_OUTPUT_DIRECTORY is the same as the installation's RUNTIME DESTINATION directory

Originally posted by @Febbe in #5620 (comment)

[bhennion]

I wouldn't do that:

• it removes flexibility, e.g. forces building the translations (dependency of the install target) even if we just want to build the test-units
• it doesn't really help: it doesn't stop the user/dev from running ./xournalpp instead of ./install/bin/xournalpp

[Febbe]

* it removes flexibility, e.g. forces building the translations (dependency of the install target) even if we just want to build the test-units

It only adds the installation to the xournalpp target, you still can build tests without it and without translations.
You can disble it, by specifying a custom installation dir.

* it doesn't really help: it doesn't stop the user/dev from running ./xournalpp instead of ./install/bin/xournalpp

Currently, it would, since ./xournalpp is not even created.

[bhennion]

I see. Then yes, something like that woud be nice!