2) I need for someone Windows-build-savvy to take a look at config/gen/icu.pl, and update the "MS VC++ requires special treatment" section to implement any changes required to get parrot to link ICU on Windows (if changes are necessary). I just don't know what needs to be done.
I may be able to do #2, or at least get someone willing to give it a shot SSH access to Oni, the windows tinder machine.
3) Right now I'm having ICU build as static (archive, .a) libraries. Long-term we'll probably want to make this a configuration option, but for the moment it saves the hassle of dealing with parrot's finding the library at runtime.
When we apply the patch I'll also take care of this--it's the only sane way to get around the breakage in Debian's sarge(testing) setup. That it means we skip a long build process and can use the system ICU install, potentially reducing our disk and memory footprint is a bonus :)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
