[Buildroot] Adding new package to toolchain, target or both ?

[Buildroot] Adding new package to toolchain, target or both ?

[Johan De Wit]

Hi,

I'm trying to build an embedded system using buildroot to be used in an
arcade cabinet, using svgalib and advancemame.  

Since svgalib is not only needed at 'runtime' in the target as dynamic
library adn/or utility programs, I also need the some files to compile
eg. advmame.  I suspect i have to add these to the toolchain to keep the
target clean.  I'm still in doubt if my 'logic' is correct and would be
glad if someone could give some advice on this issue.

Thanks

[Buildroot] Adding new package to toolchain, target or both ?

[Bernhard Fischer]

On Tue, Sep 04, 2007 at 12:07:37PM +0200, Johan De Wit wrote:
>Hi,
>
>I'm trying to build an embedded system using buildroot to be used in an
>arcade cabinet, using svgalib and advancemame.  
>
>Since svgalib is not only needed at 'runtime' in the target as dynamic
>library adn/or utility programs, I also need the some files to compile
>eg. advmame.  I suspect i have to add these to the toolchain to keep the

sort of. See libpcap/tcpdump for such an example. The lib is built and
installed into the staging_dir, the app is built using the stuff from
staging_dir and is finally installed to the target(_dir).

>target clean.  I'm still in doubt if my 'logic' is correct and would be
>glad if someone could give some advice on this issue.

HTH,
Bernhard