Skip to content
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

LCIO project should not have a top-level bin directory in its source tree #29

Closed
JeremyMcCormick opened this issue May 15, 2017 · 1 comment · May be fixed by #95
Closed

LCIO project should not have a top-level bin directory in its source tree #29

JeremyMcCormick opened this issue May 15, 2017 · 1 comment · May be fixed by #95

Comments

@JeremyMcCormick
Copy link

It is not proper for LCIO to have a top-level "bin" directory because this is the default path for executables in the install dir. So these directories interfere with each other when doing an in-source build, which is something that is done rather commonly. Instead, scripts and other programs should be put into an alternate area such as a "scripts" dir and then copied into the installation "bin" dir using install_files.

@gaede
Copy link
Contributor

gaede commented Jun 29, 2017

You are right in principle - this is some historical stuff. Why don't you provide a PR that fixes this, e.g. by moving the bin to scripts ...

@flagarde flagarde mentioned this issue Jul 31, 2020
@JeremyMcCormick JeremyMcCormick closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants