[GD-General] Practical Game Structure.

[Chris B. <Chr...@ma...>]

In the beginning of my current project I attempted to create structure within my project by using static libs. However as the project grew and the number of static libs grew my grand plan of structure has become a bit wobbly.

For example:

OpenGL Renderer is dependent on Common, Graphics and Renderer. Graphics is dependent on Common. Renderer is dependent on Application, Graphics, Video and Resource Manager. Application, Video and Resource Manager are all dependent on Common. Common includes things like expat and zlib + ~50 other classes.

From this you can assume that just about everything uses common. The problem is that since common is included and included again and again I seem to be getting linker warnings about multiply defined symbols. I've been looking for an answer to this for months, not because I get a few warnings and it looks messy, rather I get 4000 warnings and it takes a -long- time for them to be displayed, long enough that it's probably doubling my build time.

Originally I went with this structure to reduce the amount of unused code that gets linked to all my DLL's (one for each renderer, mixer, input system etc).

I'm happy to hear from anyone who can either suggest a better structure or knows how to turn a linker warning off. I'm using  .NET but this problem was with me under VC6 too.

Many thanks

Chris


NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank.