>At 02:24 PM 10/8/2006 -0700, Venkat Bommakanti wrote: >> Wondering if a "setup.cfg" for this component (TG) in the component's >> directory itself, will serve the purpose.
>Well, if each project is going to be built for only one platform, >sure. But the setup.cfg *overrides* the .pydistutils.cfg, so you don't >want to distribute a bunch of site/platform-specific options in the >project's published setup.cfg. >In any case, I thought your original issue had to do with getting >easy_install to handle these packages automatically, without modifying the >original packages in any way. And that's the context in which I've been >answering your questions. I apologize for the confusion here... Will try to clarify the full need... Basically, the need is such: . a developer would snap a <src> tree . build python <target>, TG for a <target> of choice (i686/ppc) A developer could potentially fire the build of both targets simultaneously. And to build the ppc python/TG (cross target) they'd use the necessary i686 python that is part of a <tools> directory on the i686 build box. Under those circumstances, and also the desire to keep all build related files (incuding .pydistutils.cfg or equivalents) within the source tree itself, I wanted to know the best recourse. 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. Thanks again, /venkat _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
