DLL project: single header file?

[ElectroLund]

I have a best-practices question.

I'm about to start a DLL target project to turn one of my company's custom hardware modules into a DLL for use in other projects.

This project will consist of about 5 C source files and as many header files.

But for the deliverable build output, would you recommend turning these into a single header file for the customer?  (just for convenience)

[mkossmann]

The header file , which is delivered with the DLL describes the interface for using the DLL. So a policy "one DLL comes with one header file"  makes it more easy for the user and is good practice

For building the DLL, you can  use addtional headerfiles for things, you don't want to expose to the DLL user.