My application (pksampler.sf.net) is a ground-up C++/python application. The 
root of the source tree is a kdevelop package, and the python application 
lives one directory down, while the sip-ized module lives one directory down 
that. 
Now, I'm assuming that most people develop one or the other - C module or 
python app - but has anyone found a good way for packaging an entire 
application like mine? I'm looking for some way that users can configure and 
make with options like "normal" GNU-structured projects, while maintaining 
all three packages in one tarball. 

cheers!

_______________________________________________
PyKDE mailing list    [EMAIL PROTECTED]
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde

Reply via email to