From: Daniel Frey <dmfrey+linux@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] User-space packages - Staging_Dir or Target_Dir
Date: Tue, 28 Aug 2007 07:35:03 -0400 [thread overview]
Message-ID: <b6838d3a0708280435tc49ecfbs563b3aedf3d5b57c@mail.gmail.com> (raw)
Do I need to explicitly copy what I install into the staging dir into the
root dir in order for the new libraries to be included in the resulting
image?
I have seen this done in the xml2 makefile and I wasn't sure if it was
needed for every package.
Dan
>On Wed, Aug 22, 2007 at 07:47:59PM -0400, Daniel Frey wrote:
>>When constructing my make files for my packages in the package/, what is
the
>>suggested installation directory, TARGET_DIR or STAGING_DIR?
>>
>>Some of the included packages install them to STAGING_DIR. The
>>Documentation on the buildroot website has them installed in the
TARGET_DIR.
>>
>>Is there a correct way, or preferred way?
>
>Depends :)
>
>Files that go straight to the target have to me installed to the
>TARGET_DIR. Intermediate files (prerequisites of stuff that will be on
>the target like helper libraries, headers, etc) have to live in
>STAGING_DIR. Sometimes only a small fraction of files in the staging_dir
>is needed in the real target, so they are copied selectively.
>
>HTH,
>Bernhard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20070828/84514f0e/attachment.htm
next reply other threads:[~2007-08-28 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 11:35 Daniel Frey [this message]
2007-08-28 11:48 ` [Buildroot] User-space packages - Staging_Dir or Target_Dir Thiago A. Corrêa
2007-08-28 12:30 ` Bernhard Fischer
-- strict thread matches above, loose matches on Subject: below --
2007-08-28 0:36 Daniel Frey
2007-08-22 23:47 Daniel Frey
2007-08-23 11:26 ` Bernhard Fischer
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=b6838d3a0708280435tc49ecfbs563b3aedf3d5b57c@mail.gmail.com \
--to=dmfrey+linux@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