Cegui solution structure question.
Posted: Thu Feb 26, 2009 11:13
Hi.
I'm building CeGui from source for use with Ogre and I have a question about how the CeGui solution is structured.
I notice that all configurations of the main libraries build to v0-6/bin and all configurations of the samples to v0-6/Samples/bin. By the time you have built all the different possible configurations isn't this going to become somewhat messy? I guess it isn't much of a problem having the main libraries place their output in the same location, their outputs appear to be named clearly enough, but what is the advantage of having the output of all configurations of the samples build to the same location instead of into v0-6/Samples/bin/Debug, v0-6/Samples/bin/Release, v0-6/Samples/bin/Debug_Static etc?
I ask because I'm strongly inclined to change it but I was wondering whether there was a reason it was done the way it is which I've overlooked.
I'm building CeGui from source for use with Ogre and I have a question about how the CeGui solution is structured.
I notice that all configurations of the main libraries build to v0-6/bin and all configurations of the samples to v0-6/Samples/bin. By the time you have built all the different possible configurations isn't this going to become somewhat messy? I guess it isn't much of a problem having the main libraries place their output in the same location, their outputs appear to be named clearly enough, but what is the advantage of having the output of all configurations of the samples build to the same location instead of into v0-6/Samples/bin/Debug, v0-6/Samples/bin/Release, v0-6/Samples/bin/Debug_Static etc?
I ask because I'm strongly inclined to change it but I was wondering whether there was a reason it was done the way it is which I've overlooked.