comparison docs/rendered/_sources/index.txt @ 106:1e6523de9df1

Fixed docs to represent the much-simplified build process, fixed the test target to work w/ default build options, moved doctest output dir into build dir.
author Atul Varma <varmaa@toolness.com>
date Sun, 16 Aug 2009 12:53:46 -0700
parents e455f0f00e98
children 699d03db6614
comparison
equal deleted inserted replaced
105:9d4cd0803df5 106:1e6523de9df1
64 engine's header files. 64 engine's header files.
65 65
66 * Finally, Atul has never really made a straight Python CAPI module 66 * Finally, Atul has never really made a straight Python CAPI module
67 before, so he wanted to give it a try. 67 before, so he wanted to give it a try.
68 68
69 Building and Testing 69 Building, Testing, and Installing
70 ==================== 70 =================================
71 71
72 You can either build SpiderMonkey off the mozilla-central HG 72 From the root of your pymonkey repository, run::
73 repository, or off a mirror I made of its SpiderMonkey directory. The
74 latter can be obtained here:
75 73
76 http://hg.toolness.com/spidermonkey/ 74 python setup.py build test
77 75
78 Just HG clone that repository in the root of your pymonkey repository 76 This will build the C extension and run its test suite to ensure that
79 and read the instructions in the ``README`` file to build SpiderMonkey. 77 everything works properly.
80
81 Then come back to the root of your pymonkey repository and run::
82
83 python setup.py build
84 78
85 Then run:: 79 Then run::
86 80
87 sudo python setup.py install 81 sudo python setup.py install
88 82
89 Note that if you're on Windows, you won't need the ``sudo`` bit. 83 Note that if you're on Windows, you won't need the ``sudo`` bit.
90
91 You can run the test suite by entering::
92
93 python setup.py test
94 84
95 Challenges 85 Challenges
96 ========== 86 ==========
97 87
98 There's a number of challenges that need to be resolved before 88 There's a number of challenges that need to be resolved before