From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] changing the mk file in a package
Date: Fri, 16 Feb 2007 08:15:45 +0100 [thread overview]
Message-ID: <20070216081545.cb73d4b9.philippe.ney@pardes.ws> (raw)
In-Reply-To: <20070215192046.HM.00000000000000h@daniel_ng11.bos-mail-wwl24.lycos.com>
> Hi,
>
> I'm adding a new package to buildroot. Following the standard docco I add a new
[...]
> If I do a full rebuild, I don't get the above problem. But the fully rebuild
> takes about 30 minutes! Is there a way to get a more sensible 'make' behaviour,
> so that I can avoid having to do these full rebuilds?
Hi,
Sure, juste make your target.
Say your new package as a target like
newpkg:
$(MAKE) -C $(NEWPKG_SRC)
Then, just run :
$ make newpkg
If your package doesn't depend on cramfs, you normally shouldn't have the
problem you pointed.
Philippe
next prev parent reply other threads:[~2007-02-16 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 0:20 [Buildroot] changing the mk file in a package Daniel Ng
2007-02-16 7:15 ` Philippe Ney [this message]
2007-02-16 7:32 ` Alexander Rigbo
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 4:32 [Buildroot] Changing " Daniel Ng
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=20070216081545.cb73d4b9.philippe.ney@pardes.ws \
--to=philippe.ney@pardes.ws \
--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