| Summary | It is not possible to use a UNC network path inside the -I flag for the IDL compiler. Doing so will lead to a file not found error. |
|---|---|
| Article Number | 28028 |
| Environment | Orbacus Orbix Orbix 6.3.5 Windows |
| Question/Problem Description | It is not possible on Orbix 6.3.5 in a Windows environment to use a UNC network path inside the -I flag for the IDL compiler. Doing so will lead to a file not found error.
C:/<tmp directory>/idl<id>.tmp:1: error: Can't open include file "<included file>.idl"
#include "<included file>.idl"
1 error in preprocessor.
idl: Preprocessor returned exit status 2
|
| Clarifying Information | Running IDL with a UNC network path such as:
idl -jpoa -I \\\\servername\\path idlfile.idl
will result in a Can't open include file error. |
| Error Message | C://idl.tmp:1: error: Can't open include file ".idl" #include ".idl" 1 error in preprocessor. idl: Preprocessor returned exit status 2 |
| Defect/Enhancement Number | ORB-2099, |
| Cause | |
| Resolution | Until the fix is available, use the workaround below. |
| Workaround | In order to work around this error, in a Windows environment replace the UNC server name with a mapped directory. For example: idl -jpoa -I \\\\servername\\path idlfile.idl will result in an error.
To fix this issue run:
subst z: \\\\servername idl -jpoa -I z:\\path idlfile.idl |
| Notes | |
| Attachment |
| Created date: | 24 January 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 12 May 2012 |
| First Published date: | 27 January 2012 |
#Orbix
#KnowledgeDocs
