From: Chris S. <ir0...@gm...> - 2007-03-09 12:03:56
|
Hey Keith, > 1) Not sure how I should configure, but I had to override `conf_prefix', > with `make bindist conf_prefix=', to work around what looks to me like > a Makefile bug. This voodoo to co-exist with Cygwin is a real PITA; I > really must find time to clean it up. I use this script I came up with: #!/bin/sh if [ "$1" != "install" ] && [ "$1" != "dist" ] then echo "usage: $0 [install|dist]" exit 1 fi HOST_TYPE=i386-pc-mingw32 PACKAGE=runtime PREFIX=/mingw ../../$PACKAGE/configure --build=$HOST_TYPE --host=$HOST_TYPE \ --target=$HOST_TYPE --prefix=$PREFIX make MNO_CYGWIN="-mno-cygwin" CFLAGS="-s -O3 -mtune=i686" $1 It strips the prefix so you just end up with /bin, /lib, etc. in the package (via the makefile of course). I've made the shell script such that it works both under MSYS and Cygwin (hence the no '-mno-cygwin' flag). If memory serves you compile from under Linux? That being the case, I imagine the cross-compile voodoo in the Makefile may not work for you, since the build, host and target will not all be the same. > 2) I have one manpage source, which serves for two man pages. On *nix I > would just install the first, then make either a hard or a symbolic > link to map the second; for MinGW we can't use the symlink, but a hard > link would be ok on NTFS, but a copy would be needed for FAT32. I'm > thinking it's probably best to just code a copy, and have done with it, > rather than trying to do anything clever. Any thoughts? I agree with just doing a copy, given that MSYS doesn't support links and hard links would introduce a dependency on the type of file system. Cheers! Chris -- Chris Sutcliffe http://ir0nh34d.googlepages.com http://ir0nh34d.blogspot.com http://emergedesktop.org |