Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Building zsh for multiple platforms
- X-seq: zsh-workers 461
- From: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- To: schaefer@xxxxxxxxxx
- Subject: Re: Building zsh for multiple platforms
- Date: Tue, 17 Oct 1995 14:58:29 +0100 (MET)
- Cc: zsh-workers@xxxxxxxxxxxxxxx (zsh-workers)
- In-reply-to: <951016182151.ZM4264@xxxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author