Skip to content
Snippets Groups Projects

Install MQ startup scripts and fix installation of MQ executables (#2403)

Merged Florian Uhlig requested to merge f.uhlig/cbmroot:install_MQ_scripts into master
  1. Mar 03, 2022
    • Administrator's avatar
      Don't use $VMCWORKDIR · 7f7216e1
      Administrator authored
      Use @VMCWORKDIR@ instaed which is exchanged by the acctual value while running
      CMake. In case of $VMCWORKDIR/build uses @CMAKE_BINARY_DIR@.
      7f7216e1
    • Administrator's avatar
      Correct RPATH information in the executables · 79214d74
      Administrator authored
      When building the executables the needed PATH information to find necessary
      libraries is stored in the executable. This PATH information is now also
      present in the installed executables such that they work without adding PATH
      information to the envirnonment.
      79214d74
    • Administrator's avatar
      Call the correct executable for shmem cleanup · 1f851eb8
      Administrator authored
      The cleanup of the shared memory wasn't working anymore. The executable is
      a part of FairMQ which was moved from FairRoot in its own package. Also the
      name of the excutable has changed to fairmq-shmmonitor which is now installed
      in SIMPATH.
      
      Remove blank characters from the end of lines.
      1f851eb8
    • Administrator's avatar
      Install MQ startup scripts · 31c13d83
      Administrator authored
      Create MQ startup scripts to be installed already at the configuration stage
      and store the in the build tree. The difference between the scripts used in
      the build tree and the scripts finally installed are the hardcoded directory
      information inside. In the scripts to be used inside the build directory this
      links to the source and the build directories whereas it links to the
      installation directory in case of the scripts which are installed.
      Copy the scripts during installation to the correct directory.
      Install the MQ executables in the same directory structure as in the build
      directory.
      31c13d83
Loading