Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Henrique Marks <henrique.marks@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] GCC in my pc has been used during my customize package building
Date: Thu, 28 Feb 2019 12:34:27 -0300 (BRT)	[thread overview]
Message-ID: <872494767.3516883.1551368067037.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <201902281532433257768@hoperun.com>

I was looking at the original repository.

If i were you...

I would use CMake, get rid of those handcrafted Makefiles, and integrate with buildroot using the standard Cmake integration.

Honestly, those Makefiles are not good. I know they are meant to be simple, but they are not. Notice, for instance, your usage of pkg-config to define some LDFLAGS variable. This is not going to work correctly without some manual instalation of dependencies.

This is an example, just to show you that you should use something better, but that will give less headache in the near future (for instance, now...).

I don't think the problem is in buildroot here...

----- Mensagem original -----
> De: "zhou c" <zhou_c@hoperun.com>
> Para: "buildroot" <buildroot@busybox.net>
> Enviadas: Quinta-feira, 28 de fevereiro de 2019 4:32:43
> Assunto: [Buildroot] GCC in my pc has been used during my customize package building

> Sorry, Fix the mail.
> 
> ====================================================
> 
> 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
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
Dr. Henrique Marks
henrique.marks at datacom.ind.br
R. Am?rica, 1000 - Eldorado do Sul - RS
CEP: 92990-000 - Brasil
Fone: +55 51 3933 3000 - Ramal 3466

  reply	other threads:[~2019-02-28 15:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-28  7:23 hoperun

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=872494767.3516883.1551368067037.JavaMail.zimbra@datacom.com.br \
    --to=henrique.marks@datacom.ind.br \
    --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