Short version: an installed Parrot is now able to locate its ICU data.

The longer story: During "make" a new file src/parrot_config.c is created holding currently just one entry: the install --prefix directory.
During string_init that directory is stat()ed and when the *directory* exists, ICU data are set to $prefix/blib/lib/icu/2.6.1/foo.


Using the same strategy for Parrot libs and includes (from runtime/parrot) could be a bit problematic: if Parrot got installed once, these files would always come from the installed directory, even when a newer version is in the build directory as long as the Parrot version is the same.

Comments welcome,
leo

PS I've stripped down installed files, e.g. no languages are installed. AFAIK these more or less are using "../../parrot" or such. We finally need some setting, if a language executable is able to run with an installed Parrot executable and a way to specify that for "make install". But that's probably for the next release.



Reply via email to