From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Controlling dependencies for package with manual Makefile
Date: Thu, 8 Jul 2010 09:37:40 +0200 [thread overview]
Message-ID: <20100708093740.045e621f@surf> (raw)
In-Reply-To: <8128F0FD6C26E14C8EB4BFDB92B8D6B201517E39@2putt.int.lantronix.com>
On Wed, 7 Jul 2010 10:22:25 -0700
"Matthew Davison" <matt.davison@lantronix.com> wrote:
> I understand that for packages using the autotools infrastructure, that
> the PACKAGENAME_DEPENDENCIES variable (replacing PACKAGENAME
> appropriately) is used to tell buildroot to build these dependencies
> first. Setting this variable in a manual Makefile (non-autotools based),
> does not appear to work.
>
> Is there a way to force buildroot to build package dependencies first,
> without having to convert to an autotools compliant Makefile?
As you later pointed out, it just a matter of doing:
yourpackage: yourdependency thetargetofyourpackage
However, do you have any reason for not using the AUTOTARGETS or
GENTARGETS infrastructures ? The <pkg>_DEPENDENCIES variable works with
both.
If your package is not autotools-based, you should definitely use the
GENTARGETS infrastructure. Manual Makefiles are no longer accepted in
Buildroot, and we're in the process of convering all existing packages
to GENTARGETS or AUTOTARGETS.
Don't hesitate to ask for any detail if needed.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-08 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 17:22 [Buildroot] Controlling dependencies for package with manual Makefile Matthew Davison
2010-07-08 7:37 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-07 22:26 Matthew Davison
2010-07-07 22:33 ` Yann E. MORIN
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=20100708093740.045e621f@surf \
--to=thomas.petazzoni@free-electrons.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