Sea Manky
2008.06.29, 01:17 PM
I'm at the point where I've got some solid code modules that I want to integrate into multiple projects. I'd also like to be able to fix bugs and make improvements to them while working on any given project, and have those changes reflected in the other projects that use the modules.
For instance, I've got an HID interface class that provides an interface to the user for assigning game commands to various HID controls. If I include it in a game project, and make an improvement to it in the course of this project, I'd like the changes to be reflected in the repository tree for the HID class, and therefore be available to all other projects that use it.
Ideally, the working copy for each project would have the main project code versioned under the appropriate project trunk, and my code modules versioned under their own trunks. So if I changed a code module in one project, the next time I opened a working copy of a different project that references the same module, it would get the updates.
After reading the SCM book and doing some searching, I still can't seem to find a simple way to use Subversion to do that. It looks like that I'd have to do a lot of manual branch merges for multiple projects every time I made changes to a module. Or maybe I'm missing something obvious.
So, is there any way to make this happen, is it bad practice, or am I being an idiot? :P
For instance, I've got an HID interface class that provides an interface to the user for assigning game commands to various HID controls. If I include it in a game project, and make an improvement to it in the course of this project, I'd like the changes to be reflected in the repository tree for the HID class, and therefore be available to all other projects that use it.
Ideally, the working copy for each project would have the main project code versioned under the appropriate project trunk, and my code modules versioned under their own trunks. So if I changed a code module in one project, the next time I opened a working copy of a different project that references the same module, it would get the updates.
After reading the SCM book and doing some searching, I still can't seem to find a simple way to use Subversion to do that. It looks like that I'd have to do a lot of manual branch merges for multiple projects every time I made changes to a module. Or maybe I'm missing something obvious.
So, is there any way to make this happen, is it bad practice, or am I being an idiot? :P