From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport: arch-specific workdir
Date: Sun, 04 May 2014 16:41:00 -0000 [thread overview]
Message-ID: <871tw91opk.fsf@Rainer.invalid> (raw)
In-Reply-To: <535D66EF.7080402@users.sourceforge.net> (Yaakov's message of "Sun, 27 Apr 2014 15:22:07 -0500")
Yaakov (Cygwin/X) writes:
> This is now in git master.
How about this change? I'm usually having $arch set in my shell to
divert the build results to the proper release directories, and having
yet another naming convention doesn't really help with that.
bin/cygport.in: follow Cygwin convention for directory naming (x86 instead of i686)
diff --git a/bin/cygport.in b/bin/cygport.in
index 943d391..2ecfc25 100755
--- a/bin/cygport.in
+++ b/bin/cygport.in
@@ -672,7 +672,7 @@ unset restrict
#
################################################################################
-declare -r workdir="${top}/${$PF}.${ARCH}";
+declare -r workdir="${top}/${$PF}.${ARCH/i686/x86}";
declare -r srcdir="${workdir}/src";
declare -r origsrcdir="${workdir}/origsrc";
declare -r configdir="${workdir}/config";
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
prev parent reply other threads:[~2014-05-04 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:32 cygport cross compilation Ken Brown
2014-03-19 18:05 ` Yaakov (Cygwin/X)
2014-03-19 18:28 ` Corinna Vinschen
2014-03-19 18:39 ` Ken Brown
2014-03-19 18:50 ` Ken Brown
2014-03-27 18:50 ` [RFC] cygport: arch-specific workdir (was: cygport cross compilation) Yaakov (Cygwin/X)
2014-03-27 20:01 ` [RFC] cygport: arch-specific workdir Achim Gratz
2014-03-27 21:02 ` Ken Brown
2014-03-27 23:47 ` David Stacey
2014-03-28 17:20 ` David Rothenberger
2014-04-27 20:22 ` Yaakov (Cygwin/X)
2014-05-04 16:41 ` Achim Gratz [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=871tw91opk.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).