I have a cross-platform project - Win32 and Linux - and have just imported it into EPIC running on Linux. Of course the Win32::something modules aren't installed on Linux, so EPIC gives errors for the modules that "use" them. Is there some way I can tell EPIC to ignore the offending "use" statements? Or is there another way of avoiding these error messages?
There's currently no way other than switching from 'use' to 'require' or creating dummy Win32 modules.
OK, well, that's some certainty, which is valuable in itself. I think I'll code up some dummy modules rather than mess about with the code. Thank you.