Re: [MirageOS-devel] build workflow

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

On 01/12/2016 09:19, Thomas Gazagnaire wrote:
>> - mirage configure <options> should recompile the configuration
>> according to <options>
>> - mirage build should build, and error out if the unikernel was not
>> configured upfront
> 
> How do you work with multiple target/config in parallel with this workflow? 
> Do you need to reconfigure if want to switch between backends?

Yes, atm this is the case.  There might be something on the horizon
which properly deals with multiple configs (mirage switch?).

>> - mirage clean should always remove build products (_build), not depend
>> on any concrete configuration
>> - mirage distclean (new!) should clean and remove all generated things
>> - mirage init (new, proposed by samoht) should be usable without a config.ml
> 
> I am generally ok with that workflow which improves the current one. I am 
> just a bit concerned by the number of intermediate steps and the 
> proliferation of subcommands that you need to remember. Can we try to merge 
> some of these commands? For instance maybe use `mirage clean --all` instead 
> of `mirage distclean`? And `mirage build --deps` instead of `mirage depends`? 
> etc.

I guess what we want to have is a) documentation of the workflow
(something along the lines of "topkg help release" comes into mind), b)
nice error messages if you attempt e.g. building of an unconfigured
unikernel, c) maybe a combined "mirage
justbuildeverythingandleavemealone <config-options>" subcommand.

hannes

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel