summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
691b58a)
the real configure script from the unix subdirectory, but with cwd
unchanged so that you end up doing a VPATH build in the top-level
source directory.
Should, ideally, placate the people who expect 'configure' to be at
the top level, while still letting _me_ keep all the Unix-specific
stuff in the Unix subdirectory.
git-svn-id: svn://svn.tartarus.org/sgt/putty@9241
cda61777-01e9-0310-a592-
d414129be87e
- unix/configure is for Unix and GTK. If you don't have GTK, you
should still be able to build the command-line utilities (PSCP,
- unix/configure is for Unix and GTK. If you don't have GTK, you
should still be able to build the command-line utilities (PSCP,
- PSFTP, Plink, PuTTYgen) using this script. To use it, change
- into the `unix' subdirectory, run `./configure' and then `make'.
+ PSFTP, Plink, PuTTYgen) using this script. To use it, change into
+ the `unix' subdirectory, run `./configure' and then `make'. Or you
+ can do the same in the top-level directory (we provide a little
+ wrapper that invokes configure one level down), which is more like
+ a normal Unix source archive but doesn't do so well at keeping the
+ per-platform stuff in each platform's subdirectory; it's up to you.
Note that Unix PuTTY has mostly only been tested on Linux so far;
portability problems such as BSD-style ptys or different header file
Note that Unix PuTTY has mostly only been tested on Linux so far;
portability problems such as BSD-style ptys or different header file
--- /dev/null
+#!/bin/sh
+
+$(echo "$0" | sed '$s!configure$!unix/configure!') "$@"