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

resultspace: adding explicit exec paths #174

Merged
merged 1 commit into from
Mar 27, 2015

Conversation

jbohren
Copy link
Contributor

@jbohren jbohren commented Mar 26, 2015

No description provided.

@wjwwood
Copy link
Member

wjwwood commented Mar 26, 2015

You need to make sure *_EXECUTABLE is not None (not found), otherwise you'll get an unintended failure mode.

Also, I think you should either use env | sort or just cmake -E environment. Using cmake -E environment implies you want to stay portable, but combining it with sort sort of ruins that. So whether you choose to make it portable or dependent on Unix, either way mixing cmake -E environment with sort doesn't really make sense. Any reason you decided to call out to get the env rather than use os.environ?

@jbohren
Copy link
Contributor Author

jbohren commented Mar 26, 2015

You need to make sure *_EXECUTABLE is not None (not found), otherwise you'll get an unintended failure mode.

Sure.

Also, I think you should either use env | sort or just cmake -E environment. Using cmake -E environment implies you want to stay portable, but combining it with sort sort of ruins that. So whether you choose to make it portable or dependent on Unix, either way mixing cmake -E environment with sort doesn't really make sense.

I don't mind moving sort into the python code, but I think this fix should go in regardless. Then we can open an enhancement ticket.

Any reason you decided to call out to get the env rather than use os.environ?

Because it's getting the environment from the subshell after sourcing the setup file. The only other option is to write your own script that needs to get called.

@wjwwood
Copy link
Member

wjwwood commented Mar 26, 2015

I don't mind moving sort into the python code, but I think this fix should go in regardless. Then we can open an enhancement ticket.

Sounds good to me.

Because it's getting the environment from the subshell after sourcing the setup file. The only other option is to write your own script that needs to get called.

Makes sense, I didn't notice how it was getting called before.

@wjwwood
Copy link
Member

wjwwood commented Mar 26, 2015

Just to be clear, I'm waiting on the check for None on the *_EXECUTABLE variables before merging this, but the other enhancement of not using sort can wait till later.

@jbohren
Copy link
Contributor Author

jbohren commented Mar 26, 2015

Yep.

On Thu, Mar 26, 2015, 19:44 William Woodall [email protected]
wrote:

Just to be clear, I'm waiting on the check for None on the *_EXECUTABLE
variables before merging this, but the other enhancement of not using sort
can wait till later.

Reply to this email directly or view it on GitHub
#174 (comment).

@jbohren
Copy link
Contributor Author

jbohren commented Mar 27, 2015

@wjwwood Should be good for review.

wjwwood added a commit that referenced this pull request Mar 27, 2015
resultspace: adding explicit exec paths
@wjwwood wjwwood merged commit c5f6594 into catkin:master Mar 27, 2015
@wjwwood
Copy link
Member

wjwwood commented Mar 27, 2015

lgtm

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 this pull request may close these issues.

2 participants