Re: [PATCH] Document libtool variable to_host_file_cmd.

[Ralf Wildenhues]

Hi Charles,

* Charles Wilson wrote on Fri, Sep 17, 2010 at 06:28:46PM CEST:
> * doc/libtool.texi (libtool script contents:to_host_file_cmd): Document
> variable.
> (libtool script contents:to_tool_file_cmd): Prefer `build platform'
> to `build system'; Ditto `host platform'.

> OK to push?

OK.  Why the  s/system/platform/ changes though?  I see that
libtool.texi uses platform a lot, and also uses system quite a bit but
not quite as often.  Other GNU documentation I think prefers system
however.  Or are you trying to make a distinction between both terms?
In that case, they should probably be defined somewhere (and I'd venture
to say that they are not good terms to try to differentiate, because
most users will not think there could be a difference).

Thanks,
Ralf

> --- a/doc/libtool.texi
> +++ b/doc/libtool.texi
> @@ -6822,11 +6822,21 @@ Linker flag (passed through the C compiler) used to 
> generate thread-safe
>  libraries.
>  @end defvar
>  
> address@hidden to_host_file_cmd
> +If the toolchain is not native to the build platform (e.g.@: if you are using
> +MSYS to drive the scripting, but are using the MinGW native Windows compiler)
> +this variable describes how to convert file names from the format used by the
> +build platform to the format used by host platform.  Normally set to
> address@hidden, libtool will autodetect most cases in which
> +other values should be used.  On rare occasions, it may be necessary to 
> override
> +the autodetected value (@pxref{Cygwin to MinGW Cross}).
> address@hidden defvar
> +
>  @defvar to_tool_file_cmd
> -If the toolchain is not native to the build system (e.g.@: if you are using
> +If the toolchain is not native to the build platform (e.g.@: if you are using
>  some Unix to drive the scripting together with a Windows toolchain running
>  in Wine) this variable describes how to convert file names from the format
> -used by the build system to the format used by the toolchain.  Normally set
> +used by the build platform to the format used by the toolchain.  Normally set
>  to @samp{func_convert_file_noop}.
>  @end defvar