I wanted to use cygwin because it should be as close to running on a *n*x
box as can be done on a m$ box. However I've now realised it's best to go
all or nothing; either cygwin perl, cygwin libxml, cygwin libxslt, CPAN and
cygwin make OR ActiveState Perl and ActiveState ppm. I chose the latter
because it meant less work for me :).

Regarding ppms, ActiveState don't seem to have them for AxKit (and it's
requisites) at:
http://ppm.ActiveState.com/cgibin/PPM/ppmserver.pl?urn:/PPMServer

But they can be found here:
http://theoryx5.uwinnipeg.ca/ppmpackages/

I can't say if the fully cygwin route requires no tweaking on an m$ box but
the native windows stuff with ActiveState was very good, for the most part.
There was a slight problem with the port, where it wanted to save
libxml2.dll to /perl/bin, but it did give you the opportunity to correct it
to c:\perl\bin.

Runs fine now.

(Thanks David for your help)


-----Original Message-----
From: Chris Laco [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 21:31
To: 'Adam Griffiths'; '[EMAIL PROTECTED]'
Subject: RE: AxKit on Cygwin




> -----Original Message-----
> From: Adam Griffiths [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 1:55 PM
> To: [EMAIL PROTECTED]
> Subject: AxKit on Cygwin
> 
> 
> Hi,
> Has anyone on this list managed to run AxKit with Cygwin (for
> the libxml
> libraries). If so I'd really appreciated some tips. If not, 
> what is a better
> way to get AxKit running on a PC?
> 

[Snip]

Just out of curiousity, why under Cygwin?

I've had LibXML, Sablotron,and AxKit running fine under ActiveState PErl on
Windows.
As I recall, it took just a shade of path tweaking in the Makefiles, but no
problems other than that.

I'd have to attemtp it again to remember how I got it working.

-=Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to