From 7a7b7b4f55bb042896df0788a75041c0d9029b0f Mon Sep 17 00:00:00 2001 From: Henry Fredrick Schreiner Date: Thu, 26 Apr 2018 09:36:18 -0400 Subject: [PATCH] Adding link to docs --- chapters/packages/ROOT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/chapters/packages/ROOT.md b/chapters/packages/ROOT.md index 1ab7291..d369f95 100644 --- a/chapters/packages/ROOT.md +++ b/chapters/packages/ROOT.md @@ -11,9 +11,9 @@ ROOT supports config file discovery, so you can just do: to attempt to find ROOT. If you don't have your paths set up, you can pass `-DROOT_DIR=$ROOTSYS/cmake` to find ROOT. (But, really, you should source `thisroot.sh`) -## The simple but wrong way +## The too-simple way -ROOT provides a utility to set up a ROOT project, which you can activate using `include(${ROOT_USE_FILE})`. This will automatically make ugly global variables for you. It will save you a little time setting up, and will waste massive amounts of time later if you try to do anything tricky. As long as you aren't making a library, it's probably fine for simple scripts. Includes and flags are set globally, but you'll still need to link to `${ROOT_LIBRARIES}` yourself. +ROOT [provaides a utility](https://root.cern.ch/how/integrate-root-my-project-cmake) to set up a ROOT project, which you can activate using `include(${ROOT_USE_FILE})`. This will automatically make ugly global variables for you. It will save you a little time setting up, and will waste massive amounts of time later if you try to do anything tricky. As long as you aren't making a library, it's probably fine for simple scripts. Includes and flags are set globally, but you'll still need to link to `${ROOT_LIBRARIES}` yourself. Here's what it would look like: