Welcome to the Linux DLL hell!


/* The complete definition of png_info has, as of libpng-1.5.0,
 * been moved into a separate header file that is not accessible to
 * applications.  Read libpng-manual.txt or libpng.3 for more info.
 */
That is why you should always statically link all libararies or use .Net, else some retarded maintainer will break you app "just for fun".

>>8

I'm afraid I don't have them, but since the library is open source, you could look through it and hunt down the private headers you need, copy them to your own directory, include them, and then enjoy directly manipulating the structures yourself with inlined code.

If you didn't have access to the source, I would try running the library in a debugger, and execute basic library functions that behave like getters and setters, and then observe the changes in memory values, and at what relative addresses. Then you could deduce at least part of the structure was. It would be ideal if you could automate this, but I'm not sure how one would do it. An alternative would be to generate the assembly and have a look at the entry points for these routines. If you are good at reading assembly, you may be able to locate the offsets used for manipulating the fields in the structs.