Hi all, Here's a test failure report from earlier today:
t/timerpm..........Fatal signal: Segmentation Fault (SDL Parachute Deployed) t/toolfontpm.......# Failed test (t/toolfontpm.t at line 14) # Tried to use 'SDL::Tool::Font'. # Error: Can't locate auto/SDL/TTFInit.al in @INC t/ttfontpm.........# Failed test (t/ttfontpm.t at line 14) # Tried to use 'SDL::TTFont'. # Error: Can't locate auto/SDL/TTFInit.al in @INC The first one worries me a bit, as it's a C-level error. If it comes back, we'll have to track it down. The other two are pretty simple; I don't think the user has SDL_TTF installed. If it's not there, it won't be detected or built, so obviously the tests will fail. Of course, if you don't *need* a particular chunk, there's no reason its tests should fail. We should just skip them. They'll never run, and, presumably, you know about it. My idea is to keep track of all of the extensions during configuration time, writing them to SDL::Config, then checking that in the tests. No TTF support? skip_all() in t/toolfontpm.t. That's more or less what Perl itself does in Config.pm. A plain hash is just fine, though method calls would be nicer. I also plan to add a mechanism to Build.PL where you can disable certain extensions if you like. Suggestions? Critiques? Patches? Reinterpretations of the results? -- c
