[Buildroot] Multiprojects

[Buildroot] Multiprojects

[Darcy Watkins]

Hello,

Newbie question here...

To support multiple projects, I can change the project name using
menuconfig and save the updated .config.

If I save them as proj1.config, proj2.config, etc. is there a command
line option or variable name I can set when invoking make to tell it to
choose the correct project's file?

...or do I just have to load up the file into menuconfig and save it as
.config and then run make for each case?

Thanks

Darcy

[Buildroot] Multiprojects

[Roderick Taylor]

On 11/09/2007, Darcy Watkins <DWatkins@tranzeo.com> wrote:
> Hello,
>
> Newbie question here...
>
> To support multiple projects, I can change the project name using
> menuconfig and save the updated .config.
>
> If I save them as proj1.config, proj2.config, etc. is there a command
> line option or variable name I can set when invoking make to tell it to
> choose the correct project's file?
>
> ...or do I just have to load up the file into menuconfig and save it as
> .config and then run make for each case?
>

when you want to build proj1 copy proj1.config as .config in the
buildroot directory.
invoke "make oldconfig" and then "make".  And that will build with
proj1 configuration.

[Buildroot] Multiprojects

[Ulf Samuelsson]

----- Original Message ----- 
From: "Darcy Watkins" <DWatkins@tranzeo.com>
To: <buildroot@uclibc.org>
Sent: Monday, September 10, 2007 10:51 PM
Subject: [Buildroot] Multiprojects


> Hello,
> 
> Newbie question here...
> 
> To support multiple projects, I can change the project name using
> menuconfig and save the updated .config.
> 
> If I save them as proj1.config, proj2.config, etc. is there a command
> line option or variable name I can set when invoking make to tell it to
> choose the correct project's file?
> 

Yes, and No ...
I sent in an RFC for such a patch


$ make saveconfig

will save project in 
project/<board>/<board>.config

$ make BOARD=<board> 

will use

project/<board>/<board>.config

instead of 

.config

I am thinking of using another directory than "project" though.

Search the archives for mails from me during the last two weeks.


> ...or do I just have to load up the file into menuconfig and save it as
> .config and then run make for each case?
> 
> Thanks
> 
> Darcy
> 

Best Regards
Ulf Samuelsson

[Buildroot] Multiprojects

[Darcy Watkins]

Hello Ulf,

I looked at your patch and will give it a test drive.  From what I
looked at, I think that the ...

  $ make saveconfig

... and the ...

  $ make BOARD=<board>

... should work OK, but I think that the ...

  $make getconfig

... will just overwrite the .config from the project specified from
within that .config file.  Should it be used like ...

  $make BOARD=<board> getconfig

...instead?

Regards,

Darcy

[Buildroot] Multiprojects

[Ulf Samuelsson]

> Hello Ulf,
> 
> I looked at your patch and will give it a test drive.  From what I
> looked at, I think that the ...
> 
>  $ make saveconfig
> 
> ... and the ...
> 
>  $ make BOARD=<board>
> 
> ... should work OK, but I think that the ...
> 
>  $make getconfig
> 
> ... will just overwrite the .config from the project specified from
> within that .config file.  Should it be used like ...
> 
>  $make BOARD=<board> getconfig
> 
> ...instead?

Yes.


> 
> Regards,
> 
> Darcy


Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

[Buildroot] Multiprojects

[Darcy Watkins]

Hello Ulf,

I noticed that after I cleaned up my buildroot environment to remake
from scratch and after copying in a canned config file, the .config.cmd
file was missing and needed to be generated.

(Normally this happens when you run ...

  $ make menuconfig

...etc.

For what I was doing at the time, I copied my .config to config.old and
ran...

  $ make oldconfig

... to get the .config.cmd file generated and have my canned config file
take effect.

Now my question is whether or not additional logic will be needed with
the multiprojects patch in order to ensure that the contents of
.config.cmd are appropriately sync'd up with the ability to switch
config files when invoking the make command?   (Or does the file not
need to change so all would be OK then?)

The file appears to be related to auto.conf dependency on various
Config.in files.


Regards,

Darcy