Distributing static lib

[efortier]

Hi all.

I have several classes that I'm linking into a static lib.

Now I want to provide users with the include file to use the lib, however there is plenty of stuff in the include file that most users should not see, such as internal threads stuff and the like.

We often see other people's include file very clean and even lacking some internal stuff.

How can I achieve that? Or is it a misconception on my part and my software is just badly written?


Thanks for any help.

--Eric

[Digby]

Can you split out the public declarations into a separate header file that you ship, and then create a private version to use for building the library? The private version could always include the public header.