[Distutils] cross compiling using setuptools

[Venkat Bommakanti]

>>Based on this suggestion, for the cross compile case, I tried to set:
>>   [bdist_egg]
>>   plat_name = ppc
>>but, it still insists on falling back to i686 for plat_name. Could be I'm
>>doing something fundamentally wrong.

>Dunno.  Is this in $HOME/.pydistutils.cfg?

I'm actually using a seperate <temp_dir> for each <compile_target>.
So, they are:
    <top-of-src-tree>/temp_i686/setup.cfg
and
    <top-of-src-tree>/temp_ppc/setup.cfg
They have their own (temp) set of TG comps in their native tar/zip
formats. This will allow for a developer to snap a tree and build from
there, without any build-specifc files in their $HOMEs. Each will have
    <top-of-src-tree>/temp_<tgt>/easy_install -f . TurboGears
invoked from their respective directories, and will use their respective
setup.cfg files. 

>>  'am also
>>assuming the syntax is the same for setup.cfg (local to TG source dir) and
>>pydistutils.cfg ($HOME).

>On Unix-like platforms, it's ".pydistutils.cfg" (note the '.' at the 
>beginning), NOT "pydistutils.cfg".  The latter name is used only on Windows.

Based on the above layout, and from what I've understood so far,
I'm assuming:
    <top-of-src-tree>/temp_<tgt>/setup.cfg
is the equivalent of:
    $HOME/.pydistutils.cfg
per the responses so far, and notes in pages like:
    http://docs.python.org/inst/config-syntax.html
Is is accurate to say that the contents of setup.cfg & pydistutils.cfg are the
exactly the same ?

Thanks a lot,
/venkat