From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Adding new package to toolchain, target or both ?
Date: Tue, 4 Sep 2007 23:24:17 +0200 [thread overview]
Message-ID: <20070904212417.GX11697@aon.at> (raw)
In-Reply-To: <1188900457.4793.13.camel@localhost.hobsite.be>
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
prev parent reply other threads:[~2007-09-04 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-04 10:07 [Buildroot] Adding new package to toolchain, target or both ? Johan De Wit
2007-09-04 21:24 ` Bernhard Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070904212417.GX11697@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox