[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Run tests with low max_cmd_len" on MSYS/MSVC
From: |
Ralf Wildenhues |
Subject: |
Re: "Run tests with low max_cmd_len" on MSYS/MSVC |
Date: |
Wed, 21 Jan 2009 23:16:47 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Charles Wilson wrote on Wed, Jan 21, 2009 at 11:11:22PM CET:
> Ralf Wildenhues wrote:
>
> > We may need to think about speeding up func_to_host_path, e.g., by not
> > forking for arguments that don't need conversion, or by converting
> > several paths with a constant amount of forks. But that can be done
> > separately.
>
> FWIW, as part of re-writing this:
> [PATCH] [cygwin]: Add cross-compile support to cwrapper
> http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00006.html
> I plan to split up the various case $host/case $build clauses in the
> func_to_host_path functions into separate functions. Then, using a
> configure test determine which function should be called via a libtool
> variable $build_to_host_path_cmd and $build_to_host_pathlist_cmd.
>
> The default value will be a function that simply assigns
> build_to_host_path_result=$1
>
> Then, we can target specific functions for speedups as needed.
>
> Ok plan?
Sounds like an idea.
Note that in sh one can also just define functions conditionally:
if $cond; then
func_foo ()
{
...
}
else
func_foo ...
also note that we have a section in libtool.m4 where we already define
some per-system functions which are then added literally to libtool.
That way, libtool doesn't ever contain the ones not intended for this
setup.
Cheers,
Ralf