I'm sure this situation has occured to a lot of people, but not to me before. I have a static library that I'm planning on giving to some other people to use. The interface is through an include file that contains a number of interface classes. These classes have as private members a number of structures that are defined in various other include files. I would like to be able to just give the one main .h file to the users along with the library. Doing this results in a number of undefined structures on the users side without all of the other includes. What is the prefered way (assuming there is one) of keeping these variables out of the include file the end user uses? It's not that I need to hide the existence of the structures from anyone, I just don't want to have to give them 10-15 other include files just so they can compile. Not only would this be awkward, but that would be showing a little too much of some of our internal code.