Posted by Wade Walker on Mar 03, 2014; 7:57pm
URL: https://forum.jogamp.org/Need-help-with-parsing-stdio-h-tp4031763p4031764.html

Probably the first thing to do would be to make a very small test case that demonstrates this failure. If you can make a "fail.h" with only the minimum number of lines in it, that's much easier for us to debug than all of stdio.h :)

Also, if you could show that fail.h parses correctly by changing some small thing to create "pass.h", that would narrow the problem down substantially.

Conversely, you might hack a side copy of stdio.h until it passes through gluegen (by manually precomputing the preprocessor directives that fail). Then you'd have a complete list of any other problems that gluegen might have with the file. This would tell you how far away gluegen is from being able to compile the file -- if it need tons of improvements, that's a lot more daunting than just one or two simple fixes.