If a .fbfrog file ends on a # comment with no newline after it something goes wrong, apparently an invalid pointer is followed and it errors out.
> fbfrog test.fbfrog test.h
[ 1/23] linux-x86
#include "E"
(1): could not open file: '/mnt/common/src/!lang/fbbindings/E'
where test.fbfrog contains a single byte, #, and test.h doesn't even contain any #include lines. The #include filenames I've seen are one or two characters of garbage.
An insignificant bug; I'm just filing it so I can ignore it.
If a .fbfrog file ends on a # comment with no newline after it something goes wrong, apparently an invalid pointer is followed and it errors out.
where test.fbfrog contains a single byte,
#, and test.h doesn't even contain any #include lines. The #include filenames I've seen are one or two characters of garbage.An insignificant bug; I'm just filing it so I can ignore it.