-
Notifications
You must be signed in to change notification settings - Fork 52
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
setup-environment can't handle paths with spaces #13
Comments
So we can accomodates directories with non alphanumeric characters in its name Fixed Issue #13 Change-Id: Id335b60a96f553ec99227d50c2fb0f48999ff61f Signed-off-by: Khem Raj <raj.khem@gmail.com>
So we can accomodates directories with non alphanumeric characters in its name Fixed Issue #13 Change-Id: Id335b60a96f553ec99227d50c2fb0f48999ff61f Signed-off-by: Khem Raj <raj.khem@gmail.com>
It gets a bit further and fails here:
|
thinking a bit more, I think spaces in dirname wont work with OE in general because the bblayers are split across spaces too. So it will need changes in bitbake to accommodate directories with spaces. I think you should convert space to underscores |
Fixes part of Issue #13 Change-Id: Ib8b1f9ed5f730d20c62ab0769d1c548c06814084 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Fixes part of Issue #13 Change-Id: Ib8b1f9ed5f730d20c62ab0769d1c548c06814084 Signed-off-by: Khem Raj <raj.khem@gmail.com>
You're right, bitbake/OE can't handle spaces in paths either, I've set the custom workspace var to '/build/jenkins/angstrom-v2015.06' in jenkins for now. |
From my jenkins logs:
Looks like it needs to either always use straight quotes or escape it.
The text was updated successfully, but these errors were encountered: