Rather than distrbitue 3 packages for VS2005 VS2008 and mingw32, why not package them all together and use 3 folders.
Instead of using the vclib folder we would use the vc2005lib and vc2008lib folders so that we can have both 2005 and 2008 builds if we wanted without messing around?
It would also be a lot easier to find explain and distribute.
mingVClibs suggestion
Moderator: Moderators
Re: mingVClibs suggestion
One problem with packaging them all together is that basically then one person has to maintain it. Meaning he either has to delegate, but still integrate on a change to any of the packages, or he has to maintain all of them himself, which is pretty much not doable I think.
Giving the directories separate names for different visual studio versions is definitely a good idea, if/when I make a new package I will adopt that.
Giving the directories separate names for different visual studio versions is definitely a good idea, if/when I make a new package I will adopt that.
Re: mingVClibs suggestion
Well they could be maintained as they currently are with the folder name change and when a new spring release is amde we can package them all together and say this is the libpackage0.77b1.zip and then continue as before with the separate zips until the next major release.