|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
28 May 2019, Stefan Ritt, Info, MIDAS switching to Cmake
|
28 May 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
28 May 2019, Stefan Ritt, Info, MIDAS switching to Cmake
|
29 May 2019, Stefan Ritt, Info, MIDAS switching to Cmake
|
03 Jun 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
05 Jun 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
17 Jun 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
17 Jun 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
17 Jun 2019, Stefan Ritt, Info, MIDAS switching to Cmake
|
18 Jun 2019, Konstantin Olchanski, Info, MIDAS switching to Cmake
|
|
Message ID: 1534
Entry time: 28 May 2019
In reply to: 1533
Reply to this: 1535
|
Author: |
Stefan Ritt |
Topic: |
Info |
Subject: |
MIDAS switching to Cmake |
|
|
> > - After successful compilation, all programs and libraries are in the "build" directory
> >
>
> The old "linux", "darwin", etc subdirectories go away. Makefiles for frontends and analyzers become simplified
> and can refer to MIDAS in a standard way:
>
> header files: -I$(MIDASSYS)/include
> libraries and object files: -L$(MIDASSYS)/build/lib -lmidas
> executables: PATH += $(MIDASSYS)/build/bin
Actually the library and executables go directly into the build directory (without "lib" and "bin"), so we need
header files: -I$(MIDASSYS)/include
libraries and object files: -L$(MIDASSYS)/build -lmidas
executables: PATH += $(MIDASSYS)/build
Or course that can be changed in the Cmake file, but not sure if that would be necessary/useful. |