11 Mar
2007
11 Mar
'07
12:05 p.m.
Aleksey Bragin wrote:
It's all about re-thinking what rosapps is.
Initially it was supposed
to be a place for various "app"lications. Right now it turned out to
become a kind of a trashcan, where stuff unapplicable for trunk goes.
Since this is wrong, it's perfectly fine to "force" devs to build
with rosapps (and rostests, if they are interested in thorough
testing) module.
Otherwise, with make/make all, we again end up with rudimentary rosapps.
Also there will be some kind of "unmaintained" module (undecided yet
- discussions are welcome) where some stuff from rosapps is going to
be moved (which is not currently maintained, and not interesting for
devs).
I hadn't initially realized how little had been moved over to rosapps, I
thought more had been moved out.
Upon reading the diff again, I completley agree with you.
However, this now brings me onto another thought for a faster build.
All of the modules in our tree can be classified as either core or non-core.
Lets say some core work has been done which means clean build is
required, everything is cleaned and rebuilt, even solitaire.
If a new tag was added to rbuild, 'make core', this would allow cleaning
and rebuild of the core operating system components and not everything
as it does now.
Therefore, 'make core_clean' and 'make core' would become a much faster
operation, leaving out things like explorer, control panel apps,
notepad, etc ...
Ged.