[tahoe-dev] change install.html to use setup.py instead of Make?

Brian Warner warner-tahoe at allmydata.com
Wed Sep 17 18:48:03 UTC 2008


> To saying:
> 
> """
>     1.  g++ >= v3.3 -- the "Cygwin" version of gcc/g++ works for  
> Cygwin and for Windows; the "Mac Developer Tools" version of gcc/g++  
> works for Mac
>     2. Python >= v2.4.2 including development headers i.e. "Python.h"
> 
> Run 'python setup.py build_tahoe' to build and to install the tahoe  
> executable into a subdirectory of the current directory named bin.
> 
> Run 'python setup.py trial' to verify that it built correctly and  
> passes all tests.
> """

> Yes, yes, but as I mentioned we don't need to remove the Makefile in  
> order to make this change to the install.html, right?

True.

> Why not make the change outlined above, right now?

I'm willing to do that. Two things need to be included, in my mind:

>>     1.  g++ >= v3.3, and the standard development headers and libraries --
>>         the "Cygwin" version of gcc/g++ works for Cygwin and for Windows;
>>         the "Mac Developer Tools" version of gcc/g++ works for Mac

(since robk, on an Ubuntu system, discovered that installing just g++ doesn't
get you libc-dev)


>> Run 'python setup.py build_tahoe' to build and to install the tahoe
>> executable into a subdirectory of the current directory named bin. If the
>> command encounters errors (see #455 for examples), re-run it up to three
>> times to get a successful build.

(since the Makefile currently does this for you, and I don't think we can do
the re-execute thing easily from within setup.py)

thoughts?
 -Brian



More information about the tahoe-dev mailing list