At 10:07 AM -0500 3/30/02, Josh Wilmes wrote:
>Someone said that ICU requires a C++ compiler. That's concerning to me,
>as is the issue of how we bootstrap our build process. We were planning
>on a platform-neutral miniparrot, and IMHO that can't include ICU (as i'm
>sure it's not going to be written in pure ansi C)
If the C++ bits are redoable as C, I'm OK with it. I've not taken a
good look at it to know how much it depends on C++. If it's mostly //
comments and such we can work around the issues easily enough.
If its objects, well, I suppose it depends on how much it relies on them.
>At 8:45 on 03/30/2002 EST, Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
>> At 4:32 PM -0800 3/25/02, Brent Dax wrote:
>> >I *really* strongly suggest we include ICU in the distribution. I
>> >recently had to turn off mod_ssl in the Apache 2 distro because I
>> >couldn't get OpenSSL downloaded and configured.
>>
>> FWIW, ICU in the distribution is a given if we use it.
>>
>> Parrot will require a C compiler and link tools (maybe make, but
>> maybe not) to build on a target platform and nothing else. If we rely
> > on ICU we must ship with it.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
