Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Several issues with building multiple "projects" forsame architecture
Date: Mon, 29 Oct 2007 19:22:40 +0100	[thread overview]
Message-ID: <0e7401c81a86$67de2250$090514ac@atmel.com> (raw)
In-Reply-To: d83696340710290855s5e4e4f44y7b5777bfeacf4ec2@mail.gmail.com


From: "Jonathan Nalley" <buildroot@bluebot.org>
To: <buildroot@uclibc.org>
Sent: Monday, October 29, 2007 4:55 PM
Subject: [Buildroot] Several issues with building multiple "projects" forsame architecture


>I am using the buildroot to build for several different boards, some of them
> have the same CPU architecture (PPC405GP/EP).  I have noticed some issues
> with the "project" concept in the buildroot.  Since the builds are for the
> same architecture the toolchain is created under "build_powerpc".
> Everything works fine for the first board, but for subsequent builds for
> different "project" names things are missing under
> "project_build_powerpc/PROJECT_NAME/root".  Specifically:
> 
> /root/lib/libgcc_s.so
> /root/usr/lib/libstdc++.so
> /root/usr/sbin/ethtool
> 
> This is because the make files that install those files check for:
> 
> $(GCC_BUILD_DIR2)/.libs_installed
> 
> and
> 
> $(ETHTOOL_DIR)/.installed
> 
> (There are several other packages whose make files also behave this way)
> 
> The problem with this is that the files are only installed for the first
> project, subsequent projects see the .installed file in the BUILD directory
> and think that files have already been copied to the TARGET directory.  Is
> there a reason that the buildroot relies on .installed files instead of the
> actual target file?
> 
> For example to fix ethtool I made the following change:
> 
> diff -r ff93bc269d3d buildroot/package/ethtool/ethtool.mk
> --- a/buildroot/package/ethtool/ethtool.mk      Mon Oct 29 10:03:23 2007
> -0500
> +++ b/buildroot/package/ethtool/ethtool.mk      Mon Oct 29 10:50:36 2007
> -0500
> @@ -33,11 +33,11 @@ ETHTOOL_CAT:=$(ZCAT)
> $(ETHTOOL_DIR)/ethtool: $(ETHTOOL_DIR)/.configured
>        $(MAKE) CC=$(TARGET_CC) -C $(ETHTOOL_DIR)
> 
> -$(ETHTOOL_DIR)/.installed: $(ETHTOOL_DIR)/ethtool
> +$(TARGET_DIR)/usr/sbin/ethtool: $(ETHTOOL_DIR)/ethtool
>        cp $(ETHTOOL_DIR)/ethtool $(TARGET_DIR)/usr/sbin
>        touch $@
> 
> -ethtool: uclibc $(ETHTOOL_DIR)/.installed
> +ethtool: uclibc $(TARGET_DIR)/usr/sbin/ethtool
> 
> ethtool-source: $(DL_DIR)/$(ETHTOOL_SOURCE)


It might be better to define a dependencies directory,
$(DEPENDENCIES_DIR) = project_build_dir/$(PROJECT)/depend
so you can install the ".*' files in this directory.
In many places, you just do
make DESTDIR=xxx -C <package_dir> install


Best Regards
Ulf Samuelsson

  parent reply	other threads:[~2007-10-29 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29 15:55 [Buildroot] Several issues with building multiple "projects" for same architecture Jonathan Nalley
2007-10-29 17:33 ` Bernhard Fischer
2007-10-29 18:22 ` Ulf Samuelsson [this message]
2007-10-29 22:50 ` Ulf Samuelsson
2007-10-30  0:10   ` Hamish Moffatt
2007-10-30  7:41     ` [Buildroot] Several issues with building multiple"projects" " Ulf Samuelsson

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='0e7401c81a86$67de2250$090514ac@atmel.com' \
    --to=ulf@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox