/* 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".
Name:
FrozenVoid2011-10-12 11:09
Easy: Use version <1.50 and old headers
Its not like PNG has suddenly gained x2 decode speed
you could always reverse engineer the layout of the structs and make your own headers for them, which wouldn't be that hard if you looked at the source code. It would take a while though.
Name:
FrozenVoid2011-10-12 11:37
its very useful to access structs(its faster) instead of OOP requests. LibPNG trying to 'modernise' code and remove unsafe features, replacing them with OOP walled garden because they can't code without a straitjacket. You can decode PNG with your own decoder, its just a question of time. Plus i think PPMD+Container will be far better than PNGs filter+DEFLATE in compression ratios.
Name:
Anonymous2011-10-12 12:33
>>10
Assuming spends hours reading manuals and doesnt copypaste code found on the net.