problem cloning large file (32MB) on Windows/Network Shares
Steve Borho
steve at borho.org
Sat Jan 15 17:33:34 CST 2011
On Fri, Jan 14, 2011 at 7:30 PM, Adrian Buehlmann <adrian at cadifra.com> wrote:
> On 2011-01-14 16:03, Steve Borho wrote:
>> A trick here is to use:
>>
>> python setup.py build_ext -i
>
> Interesting.
>
> Or using long options:
>
> $ python setup.py build_ext --inplace
>
>> This compiles just the C extensions, in place where they belong.
>> It's the Windows version of "make local'. It does not try to build
>> the locales, etc, which require gettext to be installed.
>
> I wondered how this could be discovered by people with some
> half-knowledge (like myself) and found this "path of discovery":
FWIW, my "path of discovery" was Mercurial's Makefile.
> Inside setup.py, at the beginning is a comment
>
> # 'python setup.py --help' for more options
>
> So I did (in cmd.exe):
>
> $ python setup.py --help
> Common commands: (see '--help-commands' for more)
> ...
>
>
> $ python setup.py --help-commands
> Standard commands:
> build build everything needed to install
> build_py "build" pure Python modules (copy to build directory)
> build_ext build C/C++ extensions (compile/link to build directory)
> ...
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> or: setup.py --help [cmd1 cmd2 ...]
> or: setup.py --help-commands
> or: setup.py cmd --help
>
>
> $ python setup.py build_ext --help
> ...
> Options for 'hgbuildext' command:
> --build-lib (-b) directory for compiled extension modules
> --build-temp (-t) directory for temporary files (build by-products)
> --plat-name (-p) platform name to cross-compile for, if supported
> (default: win32)
> --inplace (-i) ignore build-lib and put compiled extensions into the
> source directory alongside your pure Python modules
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial
>
--
Steve Borho
More information about the Mercurial
mailing list