mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] typo in ptxd_make_world_common.make?
Date: Wed, 21 Sep 2016 15:31:47 +0200	[thread overview]
Message-ID: <20160921133147.ahcq72rp6lukglhe@pengutronix.de> (raw)
In-Reply-To: <76755502-f7ac-dd61-aea7-ea541ac5798e@pengutronix.de>

Hi,

On Mon, Sep 19, 2016 at 12:11:04PM +0200, Alexander Aring wrote:
> I currently try to use some install_copy command with $(FOO_BUILDDIR)
> location for testing purpose.
> 
> Then I tried a grep on ptxdist rules file to look for an example (I
> think this exists somewhere), I did a grep on "BUILD_DIR" which is wrong
> and I got some hit at [0].
> 
> Should:
> 
> pkg_build_dir="$(call ptx/escape,$($(1)_BUILD_DIR))"
> 
> not be:
> 
> pkg_build_dir="$(call ptx/escape,$($(1)_BUILDDIR))"
> 
> and $(1) is the FOO replacement, so far I understood?

The whole thing is a bit tricky because some of the logic (foo OOT) is in
the shell code, and that's not available in your makefile.

If you don't build out of tree, then just use FOO_DIR and ignore the rest.
If you want to build out of tree, then you can:

1.
 - set FOO_BUILD_OOT = YES
 - use $(FOO_DIR)-build/
2.
 - set FOO_BUILD_DIR = $(FOO_DIR)-build
 - use $(FOO_BUILD_DIR)

Setting FOO_BUILD_DIR to anything other than FOO_DIR implies OOT.
Not that FOO_BUILD_OOT and FOO_BUILD_DIR follow the same naming theme.

FOO_BUILDDIR is a really old variable that is used the as a fallback for
FOO_BUILD_DIR if set, but should not be used. We should really remove the
handling for this.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2016-09-21 13:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 10:11 Alexander Aring
2016-09-21 13:31 ` Michael Olbrich [this message]

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=20160921133147.ahcq72rp6lukglhe@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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