-
Notifications
You must be signed in to change notification settings - Fork 18
Automate build environment #1
base: master
Are you sure you want to change the base?
Conversation
Hey @intel-aero, I noticed you guys added a new default.xml not too long ago. Is there anything on this PR that would be useful to you or should I close it? |
Thanks, @JochiPochi. I think it's very useful and improves the workflow a lot. Can you rebase this PR? |
Sure thing! |
@JochiPochi do you think you can update this soon? We are going to do a release next week and it would be good to have it in. |
I'm in the middle of testing. I'll be done by the end of the day. |
I encountered a minor error while testing, so this is delaying me a little bit, but I'm working on it. I'll keep you posted. |
@lucasdemarchi I'm testing again now that #10 seems resolved. I'll let you know once this is good for review again. |
The projects that don't have a revision with them will use the default revision introduced previously: <default sync-j="4" revision="*******"/> This simplifies upgrading the manifest file if the projects are tagged properly.
My last test is still ongoing, I synced, rebased and everything is happy now. |
The modifications to the manifest file were inspired by that of the Freescale community BSP.
https://github.com/Freescale/fsl-community-bsp-platform
The script
setup-environment
ensures that bothlocal.conf
andbblayers.conf
are set up correctly and it automatically updates to the latest version every time it runs. This ensures that a user can set up a build environment with less steps and with a lot less margin for error.setup-environment
lives on meta-intel-aero and it is meant to be used along side the following PR:intel-aero/meta-intel-aero#10
At the moment, there is an extra commit "Temp commit for testing" that should be removed before merging.
In order to test this PR, simply execute the following commands:
Make sure that the environmental variable TEMPLATECONF is not set. as it will cause the configuration to fail.