Building a ME (in ME/ directory) should now be facilitated by a build.sh script which is under construction
@mattia.gallacch I’m not sure if build.conf will help in this case. In the agency, it is related to the platform. Maybe giving the ME name in the build.sh command better, no?
Yes it could be given as argument
The script is intended to be used for configuration, building and generating the .itb file for all the MEs.
At the moment this different can be performed separately passing arguments to the script. -t to configure (defconfig), -b to compile and -d to generate the .itb. Since the building process is quite fast we could also remove the the arguments and just perform all the steps each time the script is called.
The build.sh script is not intended as a replacement for the ME/base/deploy.sh script but it makes use of it. We could merge them and keep just the build.
I guess it’s a good idea to have only one consolidated build script.
We should always have the possibility to build only one specific ME (not all MEs at each build)
New build script version works for all MEs. Takes two arguments. First is either -c (clean) or -m (build) and second is the ME name (ex. SOO.wagoled). Functionality descrpription:
- Check the existence of the corresponding “defconfig”, “.dts” and “.its” files.
- Apply config
- Create the SOO.<ME_NAME> folder
- Generate an copy the “.itb”
The ME/base/script deploy.sh has been integrated and can be removed.
Just don’t forget that for a ME (SOO.refso3 for example) there may be several defconfig/its according to the profile.
Added optional argument to specify a profile and a argument to build and deploy user space apps.
-k build kernel only
-u build user apps only
-ku build both
And removed creation of a target directory inside SOO.<ME_name>