All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] How do you add a package subdirectory?
Date: Wed, 25 Apr 2012 13:02:52 +0000 (UTC)	[thread overview]
Message-ID: <jn8slr$fpi$1@dough.gmane.org> (raw)
In-Reply-To: CAAXf6LU8+LZGYn-BQTkyjzDEQgLDkGeHrsd5WBt7NftnVfCjPg@mail.gmail.com

On 2012-04-25, Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> wrote:
> Hi Grant,
>
> On Wed, Apr 25, 2012 at 12:23 AM, Grant Edwards
><grant.b.edwards@gmail.com> wrote:
>> I'm trying to add local packages to 2012.02, and I'd like them to live
>> in a subdirectory underneath "package" (e.g. package/mycompany).
[...]
>> The "mycompany" submenu shows up where it's supposed to,
[...]
>> But, when I actually do the "make", buildroot won't attempt to build
>> packages "foo" and "bar" unless I create symlinks in the packages
>> directory that point to the corresponding directories in the mycompany
>> subdirectory
[...]

> Have a look at http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf,
> pages 27-28 where this scenario is described.

Cool.  There should be a link to this on the "Documentation" page.

> What I think you are missing is the top-level .mk file in
> /package/company/company.mk which includes all sub-mk files.

That's it.  I swear I looked for files like that and they weren't
there yesterday...

Thanks!

-- 
Grant Edwards               grant.b.edwards        Yow! If elected, Zippy
                                  at               pledges to each and every
                              gmail.com            American a 55-year-old
                                                   houseboy ...

      reply	other threads:[~2012-04-25 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 22:23 [Buildroot] How do you add a package subdirectory? Grant Edwards
2012-04-25  5:23 ` Thomas De Schampheleire
2012-04-25 13:02   ` Grant Edwards [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='jn8slr$fpi$1@dough.gmane.org' \
    --to=grant.b.edwards@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.