Thanks for replying. I'll revert the changes.
> ... however, I will say it's very strange to ship a shared library, > that has a public shlibs file, and has a -dev package that depends on > it, but the headers shipped in that -dev package are NOT the > authoritative api for that library? That's how I did it, and while it sounds odd, I believe this is right. The public interface is vnl-gen-header ... > generated.h and #include "generated.h" The generated header contains some user-facing macros that call the functions in vnlog.h with specific arguments. That's the API. From the compiler's perspective, the functions declared in vnlog.h are the interface, and the ABI in those symbols must be stable, and putting them into the .symbols file is appropriate. Let me know if I'm doing something wrong. Thanks
