James Berry wrote:
> I set up configure's selection of transcoders/msgloaders/netaccessors
> to attempt to pick the "highest value" implementation that's
> available as a default choice. That implicit ordering is accomplished
> by the ordering of the transcoders, for instance, in the case
> statement of the two-phase selection loop.
>
> In the case of transcoders, icu is considered (by me anyway) to be
> the best choice if it's available, due to its broad capabilities.
> Likewise, I think the curl netaccessor is the highest value
> netaccessor.
>
> FWIW, you can alter the selection of these things by giving "hints"
> to configure:
>
> (1) By telling it where the headers/libraries are (--with-icu=/
> icu/prefix). If it hasn't been found at all, this would cause it to
> be found and considered in priority order.
>
> (2) By telling it you really like the thing (--enable-transcoder-
> icu). This bumps the priority of the thing such that it's chosen in
> the first pass through the loop, rather than the second. Since you
> would typically give only one such hint, this is essentially an
> instruction to "use this one if it's there".
>
> (3) By telling it not to consider the thing (--disable-
> transcoder-icu). This removes the thing from consideration at all (as
> if it hadn't been found).
>
> The hints you give are thus either positive or negative influences on
> the potential selection of the thing.
Hi James,
is the above already written down in some documentation? If not, wouldn't
it be worth for an entry in the FAQs or even for Gareth's blog?
Axel
--
Humboldt-Universit�t zu Berlin
Institut f�r Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Wei�
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050
** www.freesp.de **
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
