From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@z-code.com
Cc: zsh-workers@math.gatech.edu (zsh-workers)
Subject: Re: Building zsh for multiple platforms
Date: Tue, 17 Oct 1995 14:58:29 +0100 (MET) [thread overview]
Message-ID: <199510171358.OAA26673@bolyai.cs.elte.hu> (raw)
In-Reply-To: <951016182151.ZM4264@zyrcon.z-code.com> from "Barton E. Schaefer" at Oct 16, 95 06:21:51 pm
Bart Schaefer wrote:
>
> I just tried out the trick of making a fresh directory for a new platform
> target and then running /path/to/zsh-sources/configure from the new dir.
> That seemed to work fine, so I ran "make", which also worked fine except
> that it put the final "zsh" executable in /path/to/zsh-sources/Src/zsh,
> stomping on the build I already had there.
>
> Seems to me it ought to put the executable in the same place that it puts
> the object files. Why is GNU make using the VPATH to determine the target
> directory for the executable?
I think GNU make just finds that there is a zsh bin in the target dir, and
puts the binary there. I usually make all of my binaries in a separate
directory. This does not pollute the source dir with .o, .pro etc. files, and
this way it is easier to pack a release. But if you have a bin in the source
dir you can force make to compile into the destination dir by creating an
empty zsh file in the destination dir before doing a make. Make will find it,
and will put the result there.
Bye,
Zoltan
next prev parent reply other threads:[~1995-10-17 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-17 1:21 Barton E. Schaefer
1995-10-17 13:58 ` Zoltan Hidvegi [this message]
[not found] ` <hzoli@cs.elte.hu>
1995-10-17 21:47 ` Barton E. Schaefer
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=199510171358.OAA26673@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=schaefer@z-code.com \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).