Difference between revisions of "User:Petrs"

From Cuawiki
Jump to navigation Jump to search
(Replaced content with "petrs@jlab.org +14194968602")
Line 1: Line 1:
−
<span id="anchor"></span>Setting Up ROOT (and Geant4) Development Environment on Linux with Eclipse IDE
+
petrs@jlab.org
−
 
+
+14194968602
−
ROOT and Geant4 frameworks are written in C++, a language with complete manual control over the memory. Therefore, development and execution of your ROOT script (or Geant4 program) may sometimes lead to a crash providing minimal information in the stack trace. ROOT framework does not provide out-of-the-box solutions for debugging scripts. Hence, a question about debugging ROOT scripts now and then arises in the ROOT community.
 
−
 
 
−
 
 
−
 
 
−
Generally speaking, one does not need a special development environment to invoke a debugger on a ROOT script. Users can simply invoke the GNU Debugger (GDB) on the debug the root.exe binary:
 
−
 
 
−
gdb --args root.exe -l -b -q yourRootMacro.C
 
−
 
 
−
 
 
−
 
 
−
Similarly, GDB can be used for debugging stand-alone ROOT and Geant4-based programs. However, this debugging experience is carried out in the Terminal and lacks user interface and many useful features.
 
−
 
 
−
In this article, we outline an approach for robust debugging of CERN ROOT scripts, ROOT and Geant4-based programs. We will utilize Eclipse CDT (C/C++ Development Tooling) Integrated Desktop Environment (IDE), a free software. Eclipse coupled with GDB provides enhanced code development infrastructure. Eclipse indexer scans the object-oriented hierarchy of the library classes, allowing easy navigation between C++ sources and headers, quick lookup of method overrides, code highlighting and many more. This functionality makes debugging the experience of your ROOT script or stand-alone program very efficient.
 
−
 
 
−
 
 
−
 
 
−
Additionally, the current approach allows users to have ROOT and Geant4 frameworks built in both - Release and Debug modes installed on the same computer for the same user. Debug binaries are great for development, but Release versions of the frameworks installed along with Debug versions are best at running programs with high time and space complexity.
 
−
 
 
−
 
 
−
 
 
−
A few words about the operating system (OS). In this post, we will consider the setup on Linux-based systems. A similar approach may be replicated to macOS with GNU toolchain, but will require a [https://gist.github.com/mike-myers-tob/9a6013124bad7ff074d3297db2c98247 ''code signing procedure'']. Windows is a different story.
 
−
 
 
−
 
 
−
 
 
−
Current approach outlines a setup of an extensive debugging environment for a ROOT script or ROOT/Geant4-based program. We will cover following topics:
 
−
 
 
−
* '''Install Eclipse IDE on your computer'''. Eclipse is an all-in-one development solution that automates many things: source highlighting and formatting, invokes the CMake build, lets users set breakpoints in code, attaches the debugger to the executable, and many more.
 
−
* '''Get a copy of the ROOT/Geant4 source code on your computer'''. Once attached to the project, this allows easy inspection and navigation between your script (or program) and ROOT/Geant4 source files within the IDE user interface. It also allows modification of the frameworks’ source files while debugging your program, which makes it easy to fix bugs and issue Pull Requests to the ROOT/Geant4 open-source code.
 
−
* '''Compile ROOT/Geant4 with debug symbols'''. This provides the ability to set up breakpoints in your code and original ROOT (or Geant4) source files, inspect variables, access data types and object members in the program source code.
 
−
* '''Convert your ROOT script to a standalone CMake-based C++ project'''. Once properly set up in Eclipse, existing ROOT and Geant4 Eclipse projects are referenced in your Eclipse project. This allows for re-building necessary ROOT and Geant4 source files before invoking your project build as well as sharing their indexer databases with your project.
 
−
 
 
−
<span id="anchor-1"></span>Eclipse IDE Setup
 
−
 
 
−
In this section we demonstrate how to install Eclipse IDE on a personal Linux computer. We will use Eclipse with the CMake4eclipse plugin - a powerful tool for use with CMake-based projects. Cmake4eclipse automates the project setup and allows for automatic rebuild of the frameworks’ libraries (ROOT and Geant4) once their source code was changed.
 
−
 
 
−
 
 
−
 
 
−
At this moment (July 2022) '''CMake4eclipse plugin''' provides better integration of CMake-based projects in Eclipse compared to other options e.g:
 
−
 
 
−
* Using CMake generator to create Eclipse project.
 
−
* Using the built-in Eclipse wizard to import an existing CMake project.
 
−
 
 
−
Each of these two options have its own downsides that are a subject of a separate discussion. In this article we will outline an approach featuring the CMake4eclipse plugin. For simplicity, we will enumerate the install steps below.
 
−
 
 
−
 
 
−
 
 
−
# '''Install Eclipse IDE'''. Download Eclipse installer from the [https://www.eclipse.org/downloads/ ''official website here''], extract it and run. Select “Eclipse IDE for C/C++ Developers”. Refer to the screenshot and instructions below:<br />
 
−
<br />
 
−
'''A'''. Recent Eclipse versions come with bundled Java Runtime Environment (JRE). As of July 2022, specify the built-in JRE version 11. Otherwise there will be an error accessing Eclipse help. This may be fixed in later Eclipse releases.<br />
 
−
<br />
 
−
'''B'''. On Linux it is a good practice to install user-specific applications under the “/opt” folder or home folder. In this article we will stick to the latter option and install Eclipse in the “~/Applications/” home folder for consistency with the setup on macOS.<br />
 
−
[[File:Pictures/10000201000006AB000002AD6B7D089DCDF8F063.png|624x250px]]<br />
 
−
<br />
 
−
'''C'''. Exit the wizard. There is no need to launch Eclipse right away. We will tweak its configuration file first.<br />
 
−
 
 
−
# '''Increase Eclipse memory limits'''. ROOT and Geant4 libraries contain thousands of source files. Usually, when indexing a ROOT and Geant4 based project, memory use fluctuates around 1-2GB. This can be observed via the [https://visualvm.github.io/ ''VisualVM application'']. Memory limits are specified in the “eclipse.ini” file located inside the Eclipse install folder. Use text editor to update following lines:<br />
 
−
<br />
 
−
-Xms512m<br />
 
−
-Xmx4096m (set to half of your computer RAM)<br />
 
−
<br />
 
−
Here the “-Xms” value corresponds to the initial heap size used at the Eclipse startup.''' '''The latter “-Xmx” value is to the maximum available memory limit. It is reasonable to set the “-Xmx” value to about half of the Random Access Memory (RAM) installed on the computer. Indexing speed of the ROOT and Geant4 framework source files will be higher with more available RAM.<br />
 
−
 
 
−
# '''Tweak memory limit for Eclipse indexer'''. Launch Eclipse and select default workspace location (e.g. ~Development/eclipse-workspace). In the Eclipse menu open Window → Preferences → C/C++ → Indexer. Under “Cache Limits” set:<br />
 
−
<br />
 
−
Limit relative to maximum heap size: 75%<br />
 
−
Absolute limit: 4096 MB (same as for -Xmx value in eclipse.ini)<br />
 
−
 
 
−
# '''Update Eclipse''' and its CDT plugin. In the menu select Help → Check for updates. Follow the wizard steps.<br />
 
−
 
 
−
# '''Install CMake4eclipse plugin'''. Project details can be found [https://github.com/15knots/cmake4eclipse ''on GitHub'']. In the Eclipse menu select Help → Install new software. Enter following URL in the “Work with” field: [https://raw.githubusercontent.com/15knots/CMake4eclipse/master/releng/comp-update/ ''https://raw.githubusercontent.com/15knots/CMake4eclipse/master/releng/comp-update/'']<br />
 
−
<br />
 
−
In the modal dialog uncheck the older version of CMake4eclipse (v2). Keep only version v3. Follow the wizard steps and restart Eclipse. Refer to the screenshot below:<br />
 
−
<br />
 
−
[[File:Pictures/10000201000003CA000001BB92D95A6B32146A89.png|624x285px]]<br />
 
−
 
 
−
# '''Set default workbench''' for CMake4eclipse. In the Eclipse menu select Window → Preferences → C/C++ → Cmake4eclipse → Default build system → Set &quot;Unix Makefiles&quot;.
 
−
 
 
−
 
 
−
 
 
−
 
 
−
 
 
−
Optionally apply following tweaks to the Eclipse user interface:
 
−
 
 
−
* '''Hide the Launch Bar'''. It indeed takes quite some space on smaller screens. In the Eclipse menu go to: Window → Preferences → Run/Debug → Launching → Launch Bar. Uncheck “Enable the Launch Bar”.
 
−
* '''Display line numbers'''. Eclipse menu go to: Window → Preferences → General → Editors → Text Editors. Check “Show line numbers”.
 
−
 
 
−
 
 
−
 
 
−
We successfully installed and set up the Eclipse with CMake4eclipse plugin and are now ready to set up ROOT and Geant4 projects in Eclipse IDE.
 
−
 
 
−
<span id="anchor-2"></span>Building ROOT with Debug Symbols
 
−
 
 
−
In this section we address the setup of ROOT libraries as a project in Eclipse IDE. Framework will be built with debug symbols. This allows for setting breakpoints in the ROOT code, inspecting memory and variable values during the program run.
 
−
 
 
−
 
 
−
 
 
−
# '''Install dependencies'''. Refer to [https://root.cern/install/dependencies/ ''this page on ROOT website''] to satisfy the dependencies for your system. Below we copy the list of dependencies for ROOT v6.27 for popular linux distributions. In Terminal execute following two commands:<br />
 
−
 
 
−
 
 
−
{|
 
−
|
 
−
For Ubuntu 22.04 LTS:
 
−
 
 
−
 
 
−
 
 
−
sudo apt -y install build-essential
 
−
 
 
−
 
 
−
 
 
−
sudo apt -y install git dpkg-dev cmake g++ gcc binutils libx11-dev libxpm-dev libxft-dev libxext-dev python3 libssl-dev
 
−
 
 
−
 
 
−
 
 
−
sudo apt -y install gfortran libpcre3-dev xlibmesa-glu-dev libglew1.5-dev libftgl-dev libmysqlclient-dev libfftw3-dev libcfitsio-dev graphviz-dev libavahi-compat-libdnssd-dev libldap2-dev python3-dev libxml2-dev libkrb5-dev libgsl0-dev qtwebengine5-dev
 
−
|
 
−
For Fedora 36:
 
−
 
 
−
 
 
−
 
 
−
sudo dnf -y groupinstall &quot;Development Tools&quot; &quot;Development Libraries&quot;
 
−
 
 
−
 
 
−
 
 
−
sudo dnf -y install git cmake3 gcc-c++ gcc binutils libX11-devel libXpm-devel libXft-devel libXext-devel python openssl-devel
 
−
 
 
−
 
 
−
 
 
−
sudo dnf -y install redhat-lsb-core gcc-gfortran pcre-devel mesa-libGL-devel mesa-libGLU-devel glew-devel ftgl-devel mysql-devel fftw-devel cfitsio-devel graphviz-devel avahi-compat-libdns_sd-devel openldap-devel python-devel python3-numpy libxml2-devel gsl-devel libuuid-devel readline-devel R-devel R-Rcpp-devel R-RInside-devel
 
−
|}
 
−
 
 
−
 
 
−
 
 
−
# '''Obtain the source code'''. I recommend cloning the latest ROOT from Git unless for some reason the user needs a particular version. This provides the most up-to-date code with all patches. In this guide we will keep all the source code and Git repositories under the “~/Development” home folder. In Terminal run following commands:<br />
 
−
<br />
 
−
mkdir -p ~/Development &amp;&amp; cd ~/Development<br />
 
−
git clone [https://github.com/root-project/root ''https://github.com/root-project/root'']<br />
 
−
 
 
−
# '''Set up a project in Eclipse'''. Launch Eclipse. In the menu open File → New → Project... Expand &quot;C/C++&quot; and select &quot;C++ Project&quot; (not &quot;C/C++ Project&quot;).<br />
 
−
<br />
 
−
[[File:Pictures/10000201000004DD00000281BF0871555E7C03BF.png|624x321px]]<br />
 
−
<br />
 
−
On the next dialog, specify “root” as the project name. Uncheck “Use default location” and “Browse…” for ROOT sources location (e.g. ~/Development/root). In “Project Type” expand “Cmake4eclipse” and select “Empty Project”. In “Toolchains” select “CMake driven”. Click “Next &gt;”.<br />
 
−
<br />
 
−
[[File:Pictures/1000020100000651000002CB5C78B6CA01572ACE.png|624x276px]]<br />
 
−
<br />
 
−
We are building ROOT with debug symbols. Therefore, uncheck &quot;Default&quot; and &quot;Release&quot; build options and only keep the “Debug”. Essentially this dialog box specifies the CMake -DCMAKE_BUILT_TYPE variable.<br />
 
−
<br />
 
−
Next we provide the CMake plugin with ROOT build options. Click &quot;Advanced Settings...&quot;. Go to C/C++ Build → Cmake4eclipse. Open the “CMake cache entries” tab. Add following variable names and values. Use “Add…” button on the right to input following variable names, types and values:<br />
 
−
 
 
−
 
 
−
{|
 
−
| Name
 
−
| Type
 
−
| Value
 
−
|-
 
−
| CMAKE_INSTALL_PREFIX<br />
 
−
all
 
−
| PATH<br />
 
−
STRING
 
−
| ${HOME}/Applications/root-debug<br />
 
−
ON
 
−
|}
 
−
 
 
−
<br />
 
−
When specifying variables of a PATH type, it is handy to use “File System…” button. It will display the folder picker dialog and minimize the chance of specifying a wrong path. Refer to the screenshot below:
 
−
 
 
−
 
 
−
 
 
−
[[File:Pictures/10000201000003D1000002E18A27A0EED15D2734.png|624x470px]]
 
−
 
 
−
 
 
−
 
 
−
In this tutorial we build ROOT with all optional components turned on (-Dall=ON). Please find a complete list of the [https://root.cern/install/build_from_source/#all-build-options ''ROOT CMake build variables''] on the official website and tailor your ROOT build for your needs.<br />
 
−
<br />
 
−
Click &quot;Apply and Close&quot;. Click &quot;Finish&quot;.<br />
 
−
<br />
 
−
Notice that Eclipse will start indexing the project. However, we will reschedule this operation after the build is completed. Reveal the “Progress” panel (button in the bottom right corner) and stop the indexer operation.<br />
 
−
 
 
−
 
 
−
# '''Build framework in Eclipse'''.''' '''Reveal the “Build Targets” tab (on the right side) and select &quot;root&quot; project. Right-click and select “New…” build target. Name target &quot;install&quot;. Click &quot;Ok&quot;. Expand “root” in the “Build Targets” tab and double-click the &quot;install&quot; target.<br />
 
−
[[File:Pictures/1000020100000477000002D7D8F7D7CF5EA43E6C.png|624x397px]]<br />
 
−
Build process speed depends on your computer speed and provided build variables. It may take up to a few hours to finish.<br />
 
−
<br />
 
−
'''Tip''': to switch between the CMake console and Linux make console, locate the “Display Selected Console” dropdown on the bottom actions panel.<br />
 
−
[[File:Pictures/10000201000004B700000174990E06FDF36294B6.png|624x192px]]<br />
 
−
 
 
−
# '''Exclude build folder from indexing'''. Cmake4eclipse plugin performs a so-called in-source build. Meaning that the build folder is located within a project file tree. During the build ROOT header files are copied and duplicated inside the “_build” folder. To avoid indexing duplicate sources and headers, right click “root” project → Properties → C/C++ General → Paths and Symbols → Source Location. Expand the &quot;/root&quot; folder. Select “Filter”. Click &quot;Edit filter…&quot;. Add CMake4eclipse &quot;_build&quot; folder to the filter. Click “Apply and Close”.<br />
 
−
 
 
−
# '''Run Eclipse indexer'''. We are now ready to index all ROOT source files and headers. This will create an Object-Oriented Programming (OOP) database of all ROOT object types, their methods and inheritance relations. Right click “root” project → Index → Rebuild.<br />
 
−
<br />
 
−
'''Tip 1''': sometimes the indexer may freeze while parsing the “./interpreter/…” sub-folders. If this happens, exclude the “interpreter” folder from the build (this also excludes folders from the index). Highlight the “interpreter” folder in the project tree. Right click, and select Resource Configurations → Exclude from build… Check “Debug” configuration. Click “Ok”. Now right click “root” project → Index → Rebuild.<br />
 
−
<br />
 
−
'''Tip 2''': Indexer usually takes about an hour or few to parse thousands of the ROOT framework source files. Computers with fast NVMe hard drives will perform this task the best. For older computers I strongly recommend keeping ROOT (and Geant4) sources on the RAMDisk. Please refer to my RAMDisk implementation [https://github.com/petrstepanov/tiny-ramdisk ''on GitHub''].
 
−
 
 
−
 
 
−
 
 
−
Apparently, if users would want to issue pull requests to the ROOT GitHub repository, the CMake4eclipse “_build” child folder needs to be added to the “.gitignore” of the local ROOT Git tree.
 
−
 
 
−
 
 
−
 
 
−
At this point ROOT libraries are compiled with debug symbols and Eclipse has indexed all the framework source files.
 
−
 
 
−
<span id="anchor-3"></span>Building Geant4 with Debug Symbols
 
−
 
 
−
In this section we will set up Geant4 as an Eclipse project. Skip to the next section if Geant4 install is not required. Generally speaking, the process is similar to the ROOT install since both frameworks use the CMake build system.
 
−
 
 
−
 
 
−
 
 
−
# '''Install dependencies'''. Refer to [https://geant4-userdoc.web.cern.ch/UsersGuides/InstallationGuide/html/gettingstarted.html#softwarerequirements ''the Geant4 documentation''] to satisfy its dependencies for your system. Below we provide the list of dependencies for Geant4 v10 for popular linux distributions. These packages were tested on top of the ROOT installation. Therefore make sure to install ROOT dependencies from the previous section first.<br />
 
−
 
 
−
 
 
−
{|
 
−
|
 
−
For Ubuntu 22.04 LTS
 
−
 
 
−
 
 
−
 
 
−
sudo apt install -y qt5* libX11* libXmu* libmotif* expat* libxerces-c*
 
−
|
 
−
For Fedora 36
 
−
 
 
−
 
 
−
 
 
−
sudo dnf -y install qt5* libX11* libXmu* motif* expat* mesa-libGL-devel
 
−
|}
 
−
 
 
−
 
 
−
 
 
−
# '''Obtain the source code'''. Download required Geant4 version [https://geant4.web.cern.ch/support/download ''from official website''] or clone recent codebase [https://github.com/Geant4/geant4 ''from GitHub''] under the “~/Development/geant4” folder. Please note that compared to ROOT (that has a better backward compatibility) there is a higher chance you will need to download a particular Geant4 version to satisfy a specific project you will be working on.<br />
 
−
 
 
−
# '''Set up a project in Eclipse'''. Similarly to the ROOT project setup, in the Eclipse menu open File → New → Project... Expand &quot;C/C++&quot; and select &quot;C++ Project&quot; (not &quot;C/C++ Project&quot;).<br />
 
−
<br />
 
−
On the next dialog, specify “geant4” as the project name. Uncheck “Use default location” and “Browse…” for Geant4 sources location (e.g. ~/Development/geant4). In “Project Type” expand “Cmake4eclipse” and select “Empty Project”. In “Toolchains” select “CMake driven”. Click “Next &gt;”.
 
−
 
 
−
 
 
−
 
 
−
Next we provide the CMake plugin with Geant4 build options. Click “Advanced Settings…” and navigate to C/C++ Build → Cmake4eclipse. Open the “CMake cache entries'' tab. Full list of build variables and their descriptions can be found [https://geant4-userdoc.web.cern.ch/UsersGuides/InstallationGuide/html/installguide.html#geant4-build-options ''on the Geant4 website'']. We will specify a common set of CMake variables that works for most projects:<br />
 
−
 
 
−
 
 
−
 
 
−
 
 
−
{|
 
−
| Name
 
−
| Type
 
−
| Value
 
−
|-
 
−
| CMAKE_INSTALL_PREFIX<br />
 
−
GEANT4_BUILD_MULTITHREADED<br />
 
−
GEANT4_INSTALL_DATA<br />
 
−
GEANT4_USE_GDML<br />
 
−
GEANT4_USE_OPENGL_X11<br />
 
−
GEANT4_USE_QT<br />
 
−
GEANT4_USE_XM
 
−
| PATH<br />
 
−
STRING<br />
 
−
STRING<br />
 
−
STRING<br />
 
−
STRING<br />
 
−
STRING<br />
 
−
STRING
 
−
| ${HOME}/Applications/geant4-debug<br />
 
−
ON<br />
 
−
ON<br />
 
−
ON<br />
 
−
ON<br />
 
−
ON<br />
 
−
ON
 
−
|}
 
−
 
 
−
 
 
−
 
 
−
Click &quot;Apply and Close&quot;. Click &quot;Finish&quot;.<br />
 
−
<br />
 
−
Notice that Eclipse will start indexing the project. Reveal the “Progress” panel and stop the indexer operation.
 
−
 
 
−
 
 
−
 
 
−
# '''Build framework in Eclipse'''.''' '''Reveal the “Build Targets” tab (on the right side) and select &quot;geant4t&quot; project. Right-click and select “New…” build target. Name target &quot;install&quot;. Click &quot;Ok&quot;. Expand “root” in the “Build Targets” tab and double-click the &quot;install&quot; target.<br />
 
−
 
 
−
# '''Exclude build folder from indexing'''. Right click “geant4” project → Properties → C/C++ General → Paths and Symbols → Source Location. Expand the &quot;/geant4&quot; folder. Select “Filter”. Click &quot;Edit filter…&quot;. Add CMake4eclipse &quot;_build&quot; folder to the filter. Apply changes.
 
−
 
 
−
 
 
−
 
 
−
# '''Run Eclipse indexer'''. Right click “geant4” project → Index → Rebuild. PLease note that the indexer will take a while to finish.
 
−
 
 
−
 
 
−
 
 
−
Now Geant4 libraries are compiled with debug symbols and Eclipse has indexed all the framework source files.
 
−
 
 
−
<span id="anchor-4"></span>Specifying the Environment Variables for Eclipse
 
−
 
 
−
In the above sections we compiled ROOT and Geant4 libraries with debug symbols and installed their binaries under the ~/Applications folder. However, we did not set up the required environment variables for the frameworks. Usually, one would source the environment in ~/.bashrc file:
 
−
 
 
−
 
 
−
 
 
−
source $HOME/Applications/bin/thisroot.sh
 
−
 
 
−
source $HOME/Applications/bin/geant4.sh
 
−
 
 
−
 
 
−
 
 
−
However, we will use a different approach. Frameworks built with debug symbols (-DCMAKE_BUILD_TYPE=Debug) are executed notably slower compared to the release (-DCMAKE_BUILD_TYPE=Release) versions. Some users may want to have release versions of these frameworks installed on a local computer along with the debug build.
 
−
 
 
−
 
 
−
 
 
−
To isolate ROOT and Geant4 frameworks built with debug symbols from potentially system-wide installed release versions we will source the development environment in a separate shell process where Eclipse is launched. There are a few ways to do this.
 
−
 
 
−
 
 
−
 
 
−
'''First option'''. Source ROOT and/or Geant4 variables in Terminal and manually plug them into the Eclipse settings. Open Terminal and execute following commands:<br />
 
−
 
 
−
 
 
−
source $HOME/Applications/root-debug/bin/thisroot.sh
 
−
 
 
−
source $HOME/Applications/geant4-debug/bin/geant4.sh
 
−
 
 
−
env | grep 'G4\|ROOT\|LD_LIBRARY_PATH'<br />
 
−
 
 
−
 
 
−
[[File:Pictures/10000201000003D40000017309916DD62D5443A6.png|624x235px]]
 
−
 
 
−
<br />
 
−
Required environment variables are output in the Terminal window. Now in the Eclipse menu open: Window → Preferences → C/C++ → Build → Environment. Manually “Add…” each environment variable’s name and value into the Eclipse Environment settings.
 
−
 
 
−
 
 
−
 
 
−
'''Second option'''. I consider this more elegant. We will modify the Eclipse launcher. Locate the Eclipse *.desktop launcher under the ~/.local/share/applications folder and modify the “Exec=” line as follows:
 
−
 
 
−
 
 
−
 
 
−
Exec=bash -c &quot;source \\$HOME/Applications/root-debug/bin/thisroot.sh &amp;&amp; source \\$HOME/Applications/geant4-debug/bin/geant4.sh &amp;&amp; \\$HOME/Applications/eclipse/eclipse %u&quot;
 
−
 
 
−
 
 
−
 
 
−
Please modify the path above to match your specific locations of ROOT, Geant4 and Eclipse IDE applications accordingly.
 
−
 
 
−
 
 
−
 
 
−
Now Eclipse will start in a BASH shell with correct development environment variables for your ROOT and Geant4 binaries compiled with debug symbols. The beauty of this method is that these environment variables are applied to only one particular shell process and do not affect your system-wide environment.
 
−
 
 
−
 
 
−
 
 
−
Before re-launching Eclipse please update your Linux launcher database with following command in Terminal:
 
−
 
 
−
 
 
−
 
 
−
xdg-desktop-menu forceupdate
 
−
 
 
−
 
 
−
 
 
−
Alternatively, users may simply logout and login back. Now upon a restart, Eclipse will be able to access ROOT and Geant4 development environment variables.
 
−
 
 
−
<span id="anchor-5"></span>Setting up a ROOT or Geant4-Based CMake Program
 
−
 
 
−
In this section we will set up a ROOT or Geant4-based CMake project in Eclipse IDE. This applies to stand-alone ROOT-based projects, custom Geant4 programs and examples. All Geant4 examples are CMake based. Therefore this section is useful for the users that start learning Geant4 and may want to compile and debug Geant4 examples in Eclipse IDE.
 
−
 
 
−
 
 
−
 
 
−
# '''Obtain the source code'''. Place your ROOT or Geant4-based project (Geant4 example folder) into a desired location, e.g. ~/Development.<br />
 
−
 
 
−
# '''Set up a project in Eclipse. '''Similarly to the ROOT project setup, in the Eclipse menu open File → New → Project... Expand &quot;C/C++&quot; and select &quot;C++ Project&quot; (not &quot;C/C++ Project&quot;).<br />
 
−
<br />
 
−
On the next dialog, specify your project name. Uncheck “Use default location” and “Browse…” for your project “CMakeLists.txt” location. In “Project Type” expand “Cmake4eclipse” and select “Empty Project”. In “Toolchains” select “CMake driven”. Click “Next &gt;”.<br />
 
−
<br />
 
−
On the next dialog, specify “geant4” as the project name. Uncheck “Use default location” and “Browse…” for Geant4 sources location (e.g. ~/Development/geant4). In “Project Type” expand “Cmake4eclipse” and select “Empty Project”. In “Toolchains” select “CMake driven”. Click “Next &gt;”.
 
−
 
 
−
 
 
−
 
 
−
Next we provide the CMake plugin with Geant4 build options. Since we compiled and installed ROOT and Geant4 not system-wide, but in ~/Applications home directory, we need to provide the CMake with the locations of “RootConfig.cmake” and “Geant4Config.cmake” files respectively. Therefore, “Add…” following build variable names, types and values:
 
−
 
 
−
 
 
−
 
 
−
{|
 
−
| Name
 
−
| Type
 
−
| Value
 
−
|-
 
−
| ROOT_DIR<br />
 
−
Geant4_DIR
 
−
| PATH<br />
 
−
PATH
 
−
| ${HOME}/Applications/root-debug/cmake<br />
 
−
${HOME}/Applications/geant4-debug/CMake/lib64/Geant4-10.7.3
 
−
|}
 
−
 
 
−
<br />
 
−
Make sure that the paths specified above are accurate. Some path discrepancies across frameworks’ versions may occur. Again, it’s a good idea to use Eclipse’s folder picker (“File System…” button) to make sure the path variables are correct.<br />
 
−
 
 
−
 
 
−
# '''Build project in Eclipse'''. Highlight your project in Project Explorer. Right click → build.<br />
 
−
 
 
−
# '''Reference ROOT and/or Geant4 project'''. Select your project in Project Explorer. Right click properties → Project References → Check &quot;root&quot; and/or “geant4”, depending on if your project requires . This allows following:<br />
 
−
<br />
 
−
• Sharing ROOT and/or Geant4 indexer database with your project.<br />
 
−
• Rebuild of ROOT and/or Geant4 libraries prior to your project build in case any of ROOT and/or Geant4 source files were changed.<br />
 
−
 
 
−
# '''Create a run configuration'''. Select your project in the project tree. In Eclipse menu, open Run → Debug Configurations…<br />
 
−
<br />
 
−
Select “C/C++ Application”. Press the “New launch configuration” button (on the very top left). Click the “Search Project…” button and locate the corresponding executable file.<br />
 
−
If necessary, specify any command-line parameters (macro files for Geant4 etc) on the “Arguments” tab. Click “Debug”.
 
−
 
 
−
 
 
−
 
 
−
This is it. Now you can enjoy full-scale debugging of your ROOT or Geant4 based applications in Eclipse IDE.
 
−
 
 
−
<span id="anchor-6"></span>Appendix 1. Convert a ROOT script into Standalone ROOT-based Program
 
−
 
 
−
You don’t have a CMake based project and want to use my Template GitHub project. Then your ROOT script needs to be properly integrated into the existing project. Generally speaking, this involves following:
 
−
 
 
−
 
 
−
 
 
−
* Specify extra libraries you are utilizing in project’s CMakeLists.txt.
 
−
* Explicitly define all the headers used in your script (Cling interpreter does not require that).
 
−
* Indicate certain class names in project’s LinkDef.h file for the proper dictionary and shared library generation.
 
−
 
 
−
 
 
−
 
 
−
A detailed instructions elaborating each item above can be found in this [https://github.com/petrstepanov/root-eclipse#debugging-your-personal-script ''template repository on GitHub'']. Please refer to the repository README file.
 
−
 
 
−
<span id="anchor-7"></span>Appendix 2. Standalone Geant4-based program CMake structure
 
−
 
 
−
Geant4 programs may often refer to some ROOT data types especially when saving output data in ROOT files. It is a good practice for a Geant4-based standalone application to have a nested CMake structure including some ROOT scripts or ROOT-based programs that analyze and plot Geant4 output data. Therefore, the CMake file needs to locate both frameworks.
 
−
 
 
−
 
 
−
 
 
−
An example project of a Geant4 and ROOT-based program with nested CMake structure is outlined in [https://github.com/petrstepanov/geant4-glass ''this repository on GitHub''].
 

Revision as of 18:00, 15 July 2022

petrs@jlab.org +14194968602

Retrieved from "https://wiki.jlab.org/cuawiki/index.php?title=User:Petrs&oldid=4901"