From: hoperun <hoperun@unicorn.osuosl.org>
To: buildroot@busybox.net
Subject: [Buildroot] GCC in my pc has been used during my customize package building
Date: Thu, 28 Feb 2019 15:23:14 +0800 [thread overview]
Message-ID: <20190228072314.GA2113@unicorn> (raw)
Hi all,
I am new guy in buildroot developing, and maybe have some stupid
questions.
I tried to integrate some package in github into buildroot for my
requirements. Just like the following:
################################################################################
#
# ioc-cbc-tools
#
################################################################################
IOC_CBC_TOOLS_VERSION = master
IOC_CBC_TOOLS_SITE =$(call github,intel,ioc-cbc-tools,$(IOC_CBC_TOOLS_VERSION))
IOC_CBC_TOOLS_LICENSE = BSD-3
IOC_CBC_TOOLS_LICENSE_FILES = COPYING
define IOC_CBC_TOOLS_BUILD_CMDS
$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) all
endef
define IOC_CBC_TOOLS_INSTALL_CMDS
$(TARGET_MAKE_ENV) DESTDIR=$(TARGET_DIR) $(MAKE) -C $(@D) install
endef
$(eval $(generic-package))
but the makefile in this project just like this:
$(OUT_DIR)/cbc_lifecycle: cbc_lifecycle.c
gcc -o $@ $(CFLAGS) $(LDFLAGS) cbc_lifecycle.c -pthread -lacrn-mngr
clean:
rm $(OUT_DIR)/cbc_lifecycle
It take "gcc" directly. But there isn't gcc in my "buildroot/output/host/bin".
buildroot $ find output/host/ -name "*gcc"
output/host/libexec/gcc
output/host/lib/gcc
output/host/bin/x86_64-linux-gcc
output/host/bin/x86_64-xxx-linux-gnu-gcc
Could anybody give me some hints?
Thanks for any comments.
Thanks,
Jerry
next reply other threads:[~2019-02-28 7:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 7:23 hoperun [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-28 7:32 [Buildroot] GCC in my pc has been used during my customize package building zhou_c at hoperun.com
2019-02-28 15:34 ` Henrique Marks
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=20190228072314.GA2113@unicorn \
--to=hoperun@unicorn.osuosl.org \
--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.