Why can I open files from an application that is mapped to a VxWorks processor?
Frequently, files that can be opened from your development host cannot be opened in the same way from a VxWorks processor, even if the VxWorks processor has access to the same disk drives. A possible solution is to use absolute path names instead of relative path names because VxWorks requires the latter. Another reason a file won’t open is that the value entered for a user settable string variable contains quotes. For example, if on a Gedae graph a local variable is declared as: string Filename = “/home/john/file1” then any file io box will open a file using the above string. However, if the string is changed to a user settable variable: string Filename then to open the same file you must set the filename to /home/john/file1 using the parameter setting input dialog. It is important that the name be entered into this dialog without the quotes. Note that quotes entered into the input dialog actually become part of the string and do not merely delimit the string.
Related Questions
- Why are there multiple versions of the ChemDraw CDX files within the Patent Application Data/XML v4.2 ICE and the Patent Grant Data/XML v4.2 ICE?
- How Do I Perform Certain Operations After the WaitForApplicationExit Processor Installs All Files in the Client Application Folder?
- Why can I open files from an application that is mapped to a VxWorks processor?
