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.

Sign up for GitHub

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

Jump to bottom

smithlab_cpp not allowed to be an external copy? #5

Open
andrewdavidsmith opened this issue Jul 22, 2014 · 1 comment
Open

smithlab_cpp not allowed to be an external copy? #5

andrewdavidsmith opened this issue Jul 22, 2014 · 1 comment
Labels
question

Comments

@andrewdavidsmith
Copy link
Contributor

How come there is no allowance for people who already have a SMITHLAB_CPP variable defined? Must everyone use a fresh copy hardcoded into zagros?
@pjuren
Copy link
Contributor

pjuren commented Jul 22, 2014

What is the advantage of allowing people to change it? We know the commit that is checked out with Zagros when the repos is cloned works with our code. Some other version might not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pjuren @andrewdavidsmith