Its all just a directory tree starting at /cvsroot/pure-data, so it seems somewhat arbitrary to specify a level at with each directory should be a standalone module. I do believe that there should be no sources dependencies outside of /cvsroot/pure-data (headers and libraries are a different story of course).
If you don't want to check out all of /packages/ (which is not big) you can just:
cvs co packages/Makefile.buildlayout
I originally had a Makefile.buildlayout in each of the first level directories (abstractions, externals, etc), but since they were all exactly the same file, it was a maintenance headache and seemed like a bad idea.
.hc
On Feb 6, 2006, at 11:24 AM, B. Bogart wrote:
Hey Hans,
After trying to compile HID from CVS I got this error:
Makefile:24: /home/bbogart/pd-stuff/externals/hcs/hid/../../../packages/ Makefile.buildlayout: No such file or directory make: *** No rule to make target `/home/bbogart/pd-stuff/externals/hcs/hid/../../../packages/ Makefile.buildlayout'. Stop.
I'd like to be able to compile HID without depending on the packages module. Does it make sense that one module in CVS depends on another?
Thanks,
.b.
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
________________________________________________________________________ ____
I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler