All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bzip2: Rearrange build order
Date: Wed, 05 Jun 2013 16:48:41 +0200	[thread overview]
Message-ID: <87y5aod35i.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <CAG2jQ8iYbYKBsS6Mku-NOgvdKigP9Doyy8_++joecKk7t31qRg@mail.gmail.com> (Markos Chandras's message of "Wed, 5 Jun 2013 15:25:29 +0100")

>>>>> "Markos" == Markos Chandras <markos.chandras@gmail.com> writes:

Hi,

 Markos> The problem here is that Debian uses a single Makefile to build both
 Markos> the static and the shared library but in buildroot we use
 Markos> the Makefile for the static one and Makefile-libbz2_so for the shared
 Markos> one. In this case, doing what Debian did is not possible
 Markos> but what we can do is to remove the *.o files within the
 Markos> Makefile-libbz2_so before we try to build the shared library.

Or we could just do something like:

define BZIP2_BUILD_CMDS
	$(TARGET_MAKE_ENV)
		$(MAKE) -C $(@D) libbz2.a bzip2 bzip2recover \
                        $(if $(BR2_PREFER_STATIC_LIB),,libbz2.so) \
                        $(TARGET_CONFIGURE_OPTS)
endef

E.G. only build the libbz2.so taget (which pulls in *.sho) if building
shared.

Or alternatively, keep Makefile-libbz2_so, but change it to use .sho
files instead of .o

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-06-05 14:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 12:56 [Buildroot] [PATCH] bzip2: Rearrange build order Markos Chandras
2013-06-05 13:08 ` Thomas Petazzoni
2013-06-05 13:50 ` Peter Korsgaard
2013-06-05 14:02   ` Markos Chandras
2013-06-05 14:04   ` Thomas Petazzoni
2013-06-05 14:08     ` Markos Chandras
2013-06-05 14:15     ` Peter Korsgaard
2013-06-05 14:25       ` Markos Chandras
2013-06-05 14:48         ` Peter Korsgaard [this message]
2013-06-05 15:01           ` Markos Chandras
2013-06-05 15:22       ` Thomas Petazzoni
2013-06-05 21:56         ` Peter Korsgaard

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=87y5aod35i.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.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.