Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> I've put the precompiled ICU into a directory, and supply the
>> --icushared and --icuheaders. This precompiled package contains only
>> the bin, include and lib. There's no data directory. This is because
>> the ICU built-in d
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> I've put the precompiled ICU into a directory, and supply the
> --icushared and --icuheaders. This precompiled package contains only
> the bin, include and lib. There's no data directory. This is because
> the ICU built-in data gets compiled into binary
Monday, February 14, 2005, 12:07:51 PM, Leopold Toetsch wrote:
> Ron Blaschke <[EMAIL PROTECTED]> wrote:
>> I'd like to clean up string_init, because it currently backfires
>> (segfaults) on Windows if parrot is installed (empty
>> DEFAULT_ICU_DATA_DIR ...).
> Why is DEFAULT_ICU_DATA_DIR empty? Wh
Ron Blaschke <[EMAIL PROTECTED]> wrote:
> I'd like to clean up string_init, because it currently backfires
> (segfaults) on Windows if parrot is installed (empty
> DEFAULT_ICU_DATA_DIR ...).
Why is DEFAULT_ICU_DATA_DIR empty? Where is icu actually and which
config variable is pointing at it?
Is t
I'd like to clean up string_init, because it currently backfires
(segfaults) on Windows if parrot is installed (empty
DEFAULT_ICU_DATA_DIR ...).
Could someone please tell me what string_init is supposed to do, where
it _should_ look for the ICU data directory (if at all)?
...
build_path =
