Yes, it's the cross-compiling that is the issue. But I suppose if we could build the PPM on Windows we could just copy it into the Windows distribution (which is cross-compiled on linux).

Yes, I know the SWISH module on CPAN as I'm the author. ;) That is a front-end module that uses either the SWISH::Fork module to run the swish-e executable, and there's also a SWISH::Library backend that has not been released -- and probably won't because the C API was redesigned. There's was suppose to be a SWISH::Server module, too. The idea was that code could switch between backends as needed -- something like DBI backends (well kind of).

So, basically although those modules can still work, they are really outdated for the current version of swish. The SWISH::API module makes things much easier. But since it's not pure Perl we need to get a PPM built for the Windows users.

Again, I don't know Windows, so the code I've written for running swish via the swish-e executable (like SWISH::Fork, and example CGI scripts) is a potential security problem with Windows. Under unix I can fork/exec and not worry about sending user data through the shell. I don't now how to do that with Windows, and keep the code portable (not that I've thought about it too much). But if I can get a PPM built for SWISH::API module then life will be much easier.

So you tried to build the SWISH::API module under Windows and had problems?