So, EPIC is giving me an error saying that it can't find a file. However, the file is there.
Here's a screenshot of the line that's giving me the error :
And here's the screen, only with the error tooltip showing :
I'm guessing it's doing some kind of precompilation on the source, because it knows that the file I want is called PipelineParameters.cfg. What's odd is that the message in the error tooltip is the "die" message from my code. Weird, right?
Anyway, PipelineParameters.cfg is very much there. You can see that here :
The file that's giving me the error is PipelineScripts/Pipeline/Library.pm. The file it's not finding is /PipelineScripts/PipelineParameters.cfg
Any ideas what's going on?
Thanks for the help!
Most probably a BEGIN block is going on. When you run perl -c to syntax check some code (as EPIC does for you), the content of BEGIN and END blocks is actually executed. The current working directory will be that of the script being checked, so relative paths won't work. If you want to find out where your code is being called from, you can insert something like
open(FL, ">>/tmp/foo.txt"); print FL Carp::longmess("here"); close(FL);
(and then inspect /tmp/foo.txt after performing Project > Clean…)
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.