At 02:54 PM 10/8/2006 -0700, Venkat Bommakanti wrote: >Using $HOME/.pydistutils.cfg may not be a viable option due the fact >that it'd reside outside the <snapped> source tree, and could become a >maintenance issue... Would like a solution where one gets the cfg file >(or equivalent) when they snap a tree direct... > >I was hoping something like: > <top-of-src-tree>/TurboGears/<pydistutils.cfg or setup.cfg equivalent> >with info relevant to: > > [build] > compiler = $COMPILER (native or cross-gcc) > > [bdist_egg] > plat_name = $TARGET (i686 or ppc) > exclude_source = 1 > >would let me specify (target-based) info that is picked up according >to the build target.
You could certainly put some code in setup.py that *generates* a setup.cfg based on this kind of information, if it's found in the environment, sure. _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
