[PATCH 09 v2] bootstrap: handy --base switch for bootstrapping subdirs

Daniel Hellstrom daniel at gaisler.com
Mon Feb 6 09:38:23 UTC 2012


On 02/03/2012 07:30 PM, Ralf Corsepius wrote:
> On 02/03/2012 07:14 PM, Gedare Bloom wrote:
>> On Fri, Feb 3, 2012 at 1:00 PM, Ralf Corsepius<ralf.corsepius at rtems.org>  wrote:
>>> On 02/03/2012 04:14 PM, Daniel Hellstrom wrote:
>>>>
>>>> Use the "-b/--base DIR" to process only a subdir, for example
>>>>   $ ./bootstrap --base c/src/lib/libbsp/sparc
>>>> will only generate Makefiles for all SPARC BSPs, saves some
>>>> time when working with a specific BSP.
>>>
>>>>
>>>>
>>>> Signed-off-by: Daniel Hellstrom<daniel at gaisler.com>
>>>
>>>
>>> I do not consider this change useful, because bootstrap must be run inside
>>> of the source tree. Therefore, specifying an arbitrary "basedir" is not
>>> useful.
Of course, that can be changed as well...
>>>
>> This change is intended to save time by not running bootstrap in
>> subdirectories unnecessarily. I see any time savings for bootstrap as
>> being useful; for my systems bootstrap takes as much or more time than
>> compiling rtems.
That is also my problem, and often there are only changes the the BSP one is working with at the moment.

>
> pushd <subdir in source-tree>
> ...../bootstrap
> popd
>
>>
>> By the way instead of this approach I run bootstrap from the
>> subdirectory with the changes directly, e.g.
>> cd c/src/lib/libbsp/sparc
>> $r/bootstrap
> Exactly. That's how it is supposed to be used.

Ok, I have never even thought about invoking bootstrap other than from the root directory. But it is quite complicated changing directory with lots of ../../../ ... /boostrap instead of just giving 
the path.

The problem with bootstrapping has grown since GIT was introduced is my belief, now that one can use branches flexible for the first time I find my self bootstrapping much more often than before. When 
I checkout a new branch I most of the time find myself in the root of the RTEMS sources, and at the same time I want to bootstrap. I find it handy to deal with all changes to the sources files from 
the same directory.

>
>> where my bash environment has an environment variable r that points to
>> my rtems root directory.  However I see the patched bootstrap as also
>> being useful in such situations.
> I don't. This change is dangerous.

How is it dangerous?

The above approach is quite hard when there you work with multiple repositories.

Daniel



More information about the devel mailing list