mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas@biessmann.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/2] add install-environment
Date: Thu, 1 Dec 2011 23:11:56 +0100	[thread overview]
Message-ID: <4A32BF1F-5F0F-4506-8DE3-34D94059A3B6@biessmann.de> (raw)
In-Reply-To: <20111201182239.GB32672@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 1130 bytes --]

Dear Michael,

Am 01.12.2011 um 19:22 schrieb Michael Olbrich:

> On Fri, Nov 25, 2011 at 01:40:19AM +0100, Andreas Bießmann wrote:

<snip>

>> +install-environment: all dirty-check
>> +	@echo "preparing PTXdist environment in $(DESTDIR)$(instdir)/bin ..."
>> +	@rm -fr   "$(DESTDIR)$(instdir)"
>> +	@mkdir -p "$(DESTDIR)$(instdir)"
>> +	@mkdir -p $(DESTDIR)$(instdir)/bin
>> +	@ln -sf @SED@ $(DESTDIR)$(instdir)/bin/sed
> 
> 
> I think this should happen during "make all". In many cases (especially
> when using master) an uninstalled ptxdist is used. This should not act
> differently. Something like this I think:
> 
> all: kconfig environment
> 
> kconfig:
> 	# this was "all" before
> 
> environment:
> 	# the new stuff to create the links.

But I imply to install the links to $(DESTDIR)$(instdir) which is in fact installation phase and should be separated from build phase (as it is now). So do you mean we should prepare the environment in $(PWD)/bin and then in a second step install it through tar?

> And please add python and awk as well.

Will do.

best regards

Andreas Bießmann

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 1321 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-12-01 22:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 19:53 [ptxdist] [PATCH 0/5] " Andreas Bießmann
2011-10-21 19:53 ` [ptxdist] [PATCH 1/5] " Andreas Bießmann
2011-10-21 19:53 ` [ptxdist] [PATCH 2/5] configure.ac: add check for chmod from GNU coreutils Andreas Bießmann
2011-10-27 15:10   ` Michael Olbrich
2011-10-21 19:53 ` [ptxdist] [PATCH 3/5] configure.ac: add check for mv " Andreas Bießmann
2011-10-21 19:53 ` [ptxdist] [PATCH 4/5] configrue.ac: add check for rm " Andreas Bießmann
2011-10-21 19:53 ` [ptxdist] [PATCH 5/5] configrue.ac: add check for md5sum " Andreas Bießmann
2011-11-25  0:40 ` [ptxdist] [PATCH v2 0/2] add install-environment Andreas Bießmann
2011-11-25  0:40   ` [ptxdist] [PATCH v2 1/2] " Andreas Bießmann
2011-12-01 18:22     ` Michael Olbrich
2011-12-01 22:11       ` Andreas Bießmann [this message]
2011-11-25  0:40   ` [ptxdist] [PATCH v2 2/2] configure.ac: add check for GNU coreutils Andreas Bießmann
2011-12-01 18:24     ` Michael Olbrich
2011-12-01 23:30   ` [ptxdist] [PATCH v3 0/4] add environment Andreas Bießmann
2011-12-02  7:51     ` [ptxdist] [PATCH v4 " Andreas Bießmann
2011-12-02 15:27       ` Michael Olbrich
2011-12-02  7:51     ` [ptxdist] [PATCH v4 1/4] add environment make target Andreas Bießmann
2011-12-02  7:51     ` [ptxdist] [PATCH v4 2/4] configure.ac: add check for GNU coreutils Andreas Bießmann
2011-12-02  7:51     ` [ptxdist] [PATCH v4 3/4] add awk to environment Andreas Bießmann
2011-12-02  7:51     ` [ptxdist] [PATCH v4 4/4] add python " Andreas Bießmann
2011-12-01 23:30   ` [ptxdist] [PATCH v3 1/4] add environment make target Andreas Bießmann
2011-12-01 23:41     ` Andreas Bießmann
2011-12-01 23:30   ` [ptxdist] [PATCH v3 2/4] configure.ac: add check for GNU coreutils Andreas Bießmann
2011-12-01 23:30   ` [ptxdist] [PATCH v3 3/4] add awk to environment Andreas Bießmann
2011-12-01 23:30   ` [ptxdist] [PATCH v3 4/4] add python " Andreas Bießmann

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=4A32BF1F-5F0F-4506-8DE3-34D94059A3B6@biessmann.de \
    --to=andreas@biessmann.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