[pypy-dev] is there incremental building for the translator?

Maciej Fijalkowski fijall at gmail.com
Tue Oct 6 22:51:33 CEST 2009

Also, our workflow is to test stuff on top of CPython first, so you
don't have to recompile very often (sometimes not at all).


On Tue, Oct 6, 2009 at 2:23 PM, Benjamin Peterson <benjamin at python.org> wrote:
> 2009/10/6 Philip Guo <pg at cs.stanford.edu>:
>> Hi all,
>> Sorry for another newbie question, but I'm wondering whether there is any
>> sort of "Makefile"-like incremental building functionality for the PyPy
>> translator.  I just ran:
>> cd pypy/translator/goal
>> python translate.py --opt=3 targetpypystandalone.py
>> to create pypy-c, which works perfectly, but it took about an hour on my
>> machine.  If I start hacking the PyPy source code, it seems like I have to
>> do the full translation step each time I want to create a new pypy-c.  Is
>> there any way around this?
> No, because if you make a change then the whole program has to
> retranslated to maintian invariants. What you can do, though, is speed
> up the translation process by turning off optimization and using
> --no-allworkingmodules.
> --
> Regards,
> Benjamin
> _______________________________________________
> pypy-dev at codespeak.net
> http://codespeak.net/mailman/listinfo/pypy-dev

More information about the Pypy-dev mailing list