- Install Nettle (untested! I've been using --without-nettle for
the
time beeing...)
How/where did you specify this? I've tried with make configure --without-nettle and make
--without-nettle configure
and make --without-nettle, but it keep telling me it's an
unrecognized option.
make configure CONFIGUREARGS="--without-nettle --without-bundles"
should do it. Another option is, of course, to install nettle. But I didn't bother...
/ Marcus Agehall (Scanian)
Previous text:
2004-05-19 11:00: Subject: Re: Pike @ win32
Marcus Agehall (Scanian) @ Pike (-) developers forum wrote:
I've just committed an initial patch that allows Pike to be compiled using mingw32.
Thanks!
To compile pike using mingw32, you will have to do the following:
[snip]
- Install Nettle (untested! I've been using --without-nettle for the
time beeing...)
How/where did you specify this? I've tried with make configure --without-nettle and make --without-nettle configure and make --without-nettle, but it keep telling me it's an unrecognized option.
- Get a Pike 7.7 source snapshot (or build one yourself). Building
from CVS under mingw32 seems to break due to some cr/lf problem, so build the source-dist on a unix box. 7) Set the PIKE_PATH_TRANSLATE to some sed-command which translates the master-paths from you MSYS installation to the regular NT-CMD filesystem(*). 8) Do "make configure" to configure your buildtree. 9) Do "make" do build pike. 10) (optional) Do "make verify". This will fail, the hard way.. ;( 11) You should now have a pike which is usable to some extent. I havn't tested it much, but I've done some simple tests and it seems to hold up fairly well.
(*) I build from my home-dir, /home/SSS668. To create a working master, I need to translate that path to c:/msys/1.0/home/SSS668. You need to do the same using some creative sed-command
[snip]
Thought I'd post an example (what I have): export PIKE_PATH_TRANSLATE="sed s@/dev@f:/work/dev@g"
I'm building in /dev/pike/Pike-v7.7-snapshot which should point to f:/work/dev/pike/Pike-v7.7-snapshot it works as expected with pwd | $PIKE_PATH_TRANSLATE so I hope it does the trick.
Running configure now (with nettle, I suppose) see how it goes :o)
// Andreas
/ Brevbäraren