-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy cafe to build directory so we don't have to run mrbslp #110
base: develop
Are you sure you want to change the base?
Conversation
… to run cafe script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR clarifies well the need for the first change, but I miss the explanation for the second one.
@@ -98,7 +98,7 @@ void load_cafana_libs() | |||
gROOT->Macro("${SBNANA_FQ_DIR}/bin/rootlogon.C"); | |||
} | |||
else{ | |||
gROOT->Macro("${MRB_BUILDDIR}/sbnana/bin/rootlogon.C"); | |||
gROOT->Macro("${SBNANA_DIR}/sbnana/CAFAna/rootlogon.C"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This new version appears to mirror the setup strategy in cafe
script.
Nevertheless I do not understand the motivation of this change. Can you explain?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without this PR, users ran mrbslp
before they run cafe
. ${SBNANA_FQ_DIR}
is only set after mrbslp
, and for this case it looks for "${SBNANA_FQ_DIR}/bin/rootlogon.C"
which exists. This PR helps user to run cafe
without running mrbslp
, and there we have empty ${SBNANA_FQ_DIR}
. I then found we don't have "${MRB_BUILDDIR}/sbnana/bin/rootlogon.C", but it exists under "${SBNANA_DIR}/sbnana/CAFAna/rootlogon.C"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While checking more on this, it looks like just using tagged sbnana
with setup sbnana v09_75_03 -qe20:prof
does not suffer from this issue, where most of the users (I guess) check out the product and use local products
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you setup
sbnana
(either explicitly or indirectly with mrbslp
), SBNANA_FQ_DIR
is set so this part of the code would be skipped. That could explain your last statement.
@jedori0228 @PetrilloAtWork What's the status of this PR? I'm preparing a release and would like to include all open PRs that can be pushed. let me know! |
is this PR still needed? @jedori0228 ? |
It is not necessary, but at leaset helping me a lot.. I don't have to keep doing |
@jedori0228, have you considered using |
I am not sure which is the better solution, actually. |
cafe
script is not seen from thebuild
directory, but only copied tolocalProducts
during theinstall
step.mrbsetenv
appends thebuild
directory to${PATH}
, so users have to runmrbslp
to uselocalProducts
instead. (and then had to runmrbsetenv
to compile the code, and thenmrbslp
to runcafe
...)This fix copies the script to
build
directory and then copies it again tolocalProducts
duringinstall
, so can runcafe
without runningmrbslp
.