Hi, I'm working with Blink and have a couple of basic questions. - What environment variables control the directories searched when you use an #include statement? - Is there a way to get more verbose output when a kernel fails to compile or run? --- Sometimes I get 'Error running kernel' in a red bar over the Nuke viewer and that's it. --- If there's a syntax error in an included header and the compilation fails, you only get the warning that the compilation failed. If the error is in the main .blink file being loaded, you get proper information about which line has the problem and what mistake you've made.
Is there a secret blink.log file somewhere on disk with lots of verbose output from the compiler and runtime? Thanks in advance for your help. I'm having fun playing with Blink thus far. HP
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
