Thanks! I think that looks like a good model and I may adopt it. Where do you actually place the distribution for packaging?
Randolph On 2009-12-14, Fabio Zadrozny <fabi...@gmail.com> wrote: > Not sure if there's a 'standard' practice, but usually I work as: > > /project > /build <- contains several build utilities (SConstruct, an > install.py used for code-generation, etc). > /libs <- contains generated dlls (when doing 32/64 builds there's > a directory inside making the distinction). > /source > /python <- this is the actual source folder for python > /c++ <- c++ source files > /c++ bindings <- these are only wrappings for c++ to python > (each submodule generates a dll to be imported in python). > > Cheers, > > Fabio > > > > On Mon, Dec 14, 2009 at 6:39 PM, Randolph Fritz <rfritz...@gmail.com> wrote: >> What's current practice for organizing a cross-platform mixed >> Python/C++ project directory? Source files under src, obviously. But >> what about build files? Do I include the python sources in the >> distribution? How do I keep the various platform-dependent files >> separate? >> >> Anyone got a book or a link to recommend? Any specific tips or >> gotchas you'd like to mention? >> -- >> Randolph Fritz >> design machine group, architecture department, university of washington >> rfr...@u.washington.edu -or- rfritz...@gmail.com >> >> >> ------------------------------------------------------------------------------ >> Return on Information: >> Google Enterprise Search pays you back >> Get the facts. >> http://p.sf.net/sfu/google-dev2dev >> _______________________________________________ >> pydev-code mailing list >> pydev-code@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/pydev-code >> > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev -- Randolph Fritz design machine group, architecture department, university of washington rfr...@u.washington.edu -or- rfritz...@gmail.com ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ pydev-code mailing list pydev-code@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pydev-code
