On Sat, 23 Jul 2005, Adrian Bunk wrote:
> On Tue, Jul 19, 2005 at 10:50:53PM +0200, Bodo Eggert wrote:
> > OTOH, the build system
> > should automatically propagate the dependencies. I asume that should be
> > easy, except for having the time to implement that.
> >...
>
> There are nontrivial problems:
> E.g. what should happen if you select option A that depends on (B || C)?
You should in effect depend on ($original_depends) && (B || C). You'll
just need to append all (recursive) dependencies in the selecting option.
last_length:=-1; /* impossible value */
while |options_with_unresolved_selects| > 0 do begin
if |options_with_unresolved_selects| == last_length
then goto circular_recursion_detected;
last_length:=|options_with_unresolved_selects|;
for i in options_with_unresolved_selects do begin
for s in i->unresolved_selects do
if 0 == |s->unresolved_selects|
then begin
add(i->depends, s->depends)
delete_from(i->unresolved_selects, s)
end
if 0 == |i->unresolved_selects|
then delete_from(options_with_unresolved_selects, i);
end
end
> There's one opinion that options should be either select'able _or_ user
> visible.
That would only result in ugly workarounds. Think about the kernel
libraries. You'll want to manually select them, and you'll want to
automatically select them, and you want both to be visible.
--
Funny quotes:
22. When everything's going your way, you're in the wrong lane and and going
the wrong way.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
