Re: RFC: multi-sourced file, multiple choice 'instanciations'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

[Not sure if you will ever read this mail as you seem to block my traffic.]

On Tue, Dec 14, 2010 at 6:34 PM, Yann E. MORIN
<yann.morin.1998@xxxxxxxxxxxxxxx> wrote:
> Hello All!
>
> For a project I'm maintaining, crosstool-NG [0], I'm using Kconfig to setup
> the configuration.
>
> In this context, I have the need for options that are common to multiple,
> exclusive components (each a boolean in a choice). Each component also
> has its own set of options. What makes it complex is that, given three
> components, only two have the common options, while the third will not.
> See [1] for an example of such a (limited, yet representative) setup.
>
> But currently, mconf refuses to include the same files more than once:
>  component-2.in:12: file 'common.in' is already sourced from 'component-1.in'
>
> This is trivial to 'fix', when the multi-sourced file does not have choices
> in it, that is only bools, strings, ints... Just yank the 6-or-so lines that
> are responsible for the check.
>
this open the way to infinite inclusion loop.

I need to check the code for the rest.

 - Arnaud
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux&nblp;USB Development]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite Secrets]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux