http://www.pragmaticprogrammer.com/
Get their CVS book, their project automation book, their unittesting book, and maybe others that sound interesting.
Great reads, great information in a package you can actually use.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
Those books will help you set things up and decide what to put in CVS and what not :)
hooknc is right in stating that build artifacts typically have no place in your VCS (certainly not in the project that creates them) and that you should slice up your system in logically independent parts and handle those as separate (sub)projects.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337
If you're using 3rd party libraries (which seems to be the case here) there's nothing wrong with storing those in binary form as that's the only form you have.
jwenting
duckman
8,392 posts since Nov 2004
Reputation Points: 1,662
Solved Threads: 337