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

Add rock-find-root and rock-source-env shell helpers #26

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add rock-find-root and rock-source-env shell helpers #26

wants to merge 1 commit into from

Conversation

2maz
Copy link
Member

@2maz 2maz commented Feb 24, 2016

This adds shell functions to facilitate sourcing the env.sh when working with multiple projects on the same machine: 'rock-source-env' crawls the directory hierarchy backwards to find and source the currently relevant env.sh

Pls do not merge yet, just comment.

@doudou
Copy link
Member

doudou commented Feb 24, 2016

Isn't that aenv here: https://rock.opendfki.de/wiki/WikiStart/Toolchain/MultipleInstalls

Nothing against it per se. The only reason aenv stayed outside of this file is that you obviously can't use the helpers from this file before you sourced the first env.sh

@2maz
Copy link
Member Author

2maz commented Feb 24, 2016

Ok, seems I missed or forgot about that -- one more reason I see to embed the code into autoproj or base/script.
Though there is a slight difference still. I like to avoid the autoloading part, i.e. requiring still to call aenv or similar in the shell.

@doudou
Copy link
Member

doudou commented Aug 25, 2016

Ok, seems I missed or forgot about that -- one more reason I see to embed the code into autoproj or base/script.

The problem is that you can't have it available - even if in base/scripts - before you sourced env.sh. It's a chicken-and-egg problem.

Generally speaking, if you find a good workflow around this, I think it would be very welcome in autoproj - I don't see the reason to put it inside Rock-specific stuff.

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