All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: alsa-devel@alsa-project.org
Subject: Making only some targets on cross-compilation
Date: Thu, 20 Aug 2009 17:49:35 -0700	[thread overview]
Message-ID: <4A8DEF1F.5000205@redfish-solutions.com> (raw)

Hi.

I'm working on the astlinux project (www.astlinux.org) and had a
question about doing a build for only a subset of the $SUBDIRS targets.

I tried doing something like:

make -C $(ALSA-LIB_DIR) \
  SUBDIRS='src include modules aserver'



but this fails. The problem is that if we look into the environment in
the top-level $(RECURSIVE_TARGETS): we get:

SUBDIRS=include src modules aserver
...
MAKEFLAGS=w --jobserver-fds=3,4 -j -- SUBDIRS=include\ src\ modules\ aserver CC=/home/philipp/asterisk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc



so those targets eventually get picked up by the make running in
include/, which then overrides his own Makefile value:

SUBDIRS = sound


and tries to build the same top-level targets now in include/. Clearly
this is wrong.

Anyone have a work-around to this?  We're on an embedded system, and
don't want to build (nor install, obviously) "doc", "test", "alsalisp",
"utils", etc.

Having something like:

SUBDIRS=$(filter-out $(SUBDIRS_EXCLUDE),$(SUBDIRS))

would be really sweet.  Then I could just build as:

make -C $(ALSA-LIB_DIR) \
    all SUBDIRS_EXCLUDE='doc test utils'

and only get the targets I want...

Thanks,

-Philip

                 reply	other threads:[~2009-08-21  0:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4A8DEF1F.5000205@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=alsa-devel@alsa-project.org \
    /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.