From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Can't build customized packages
Date: Thu, 15 Feb 2018 19:35:28 +0100 [thread overview]
Message-ID: <20180215193528.043ea476@gmx.net> (raw)
In-Reply-To: <CAPzckP4HAA7mSPAr+vFgyjNihRhB805cbev_gxJAz4RCqK5Ezw@mail.gmail.com>
On Thu, 15 Feb 2018 18:48:17 +0100, Sjoerd Venema <srg.venema@gmail.com> wrote:
Hello Sjoerd,
> Hi,
>
> I'm probably missing something basic here, but I can't see it. Any way, I
> have created a number of custom packages, which I have grouped under a
> sub-directory of packages.
>
> I have added a Config.in to that sub-directory ("packages/arctura"... see
> link below), which makes everything selectable in the "make
> menuconfig"-menu. So far, so good.
>
> However, I noticed that the packages are not being build. And running make
> <custom package> returns a "No rule to make target" error.
>
> I hadn't added a <company>.mk makefile ("actura.mk", see link below) yet,
> so I did, according to the documentation, but no difference.
>
> My setup can be seen here:
> https://github.com/Sjoerd82/buildroot/tree/master/buildroot-2017.08
diff -u package/arctura/arctura.mk_orig package/arctura/arctura.mk
--- package/arctura/arctura.mk_orig 2018-02-15 19:32:11.572197327 +0100
+++ package/arctura/arctura.mk 2018-02-15 19:32:23.460406475 +0100
@@ -1 +1 @@
-include $(sort $(wildcard package/<company>/*/*.mk))
+include $(sort $(wildcard package/arctura/*/*.mk))
Regards,
Peter
>
> Thanks
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
prev parent reply other threads:[~2018-02-15 18:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:48 [Buildroot] Can't build customized packages Sjoerd Venema
2018-02-15 18:35 ` Peter Seiderer [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=20180215193528.043ea476@gmx.net \
--to=ps.report@gmx.net \
--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.