[Chandler-dev] Troubles running debug Chandler under Leopard

[Robin Dunn]

Andi Vajda wrote:
> 
> On Tue, 11 Dec 2007, Andi Vajda wrote:
> 
> I should add that debug builds on partial build OSs are only marginally 
> useful. I've had to force a complete debug build on Gutsy/Feisty to be 
> able to do actual debugging of a crash that involved python.
> 
> On Linux, you can do a full build (and a full install in chandler) by 
> forcing DISTRIB_CODENAME to be something else than gutsy or feisty:
> 
>   - cd external
>   - make DISTRIB_CODENAME=linux DEBUG=1
>   - make DISTRIB_CODENAME=linux DEBUG=1 binaries install
>   - cd internal
>   - make DISTRIB_CODENAME=linux DEBUG=1
>   - make DISTRIB_CODENAME=linux DEBUG=1 binaries install
>   - cd chandler
>   - make DISTRIB_CODENAME=linux DEBUG=1 install
> 
> Again, when doing such a thing, it is best to start from a complete 
> clean tree as you're now building your own debug python and all binary 
> packages built with python need to be installed in the correct 
> site-packages for a local build (as opposed to a partial build 
> site-packages that is using the system python).
> 
> I'm afraid that on Leopard there is no such obvious trick at the moment 
> but that it would be relatively easy to add.

You can do it by setting OS_MAJOR_VER=8.


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!