!ObjAsm cannot import/get header files
Bill Antonia (2466) 130 posts |
I’ve been trying to add: GET SWIsor GET Hdr:SWIsto the beginning of my code to import SWI names. However in the throwback it shows an error stating that the file could not be opened, the path being relative to the source I’m trying to assemble. I have checked that the !SetPaths has been run by executing the following in a task window: echo <Hdr$Path> All seems fine there. Does anyone have any clues how to fix this issue? |
Steve Pampling (1551) 8170 posts |
Check whether that header is actually present on the defined hdr$path. (Or anywhere in the DDE directories) |
Bill Antonia (2466) 130 posts |
Within the output from the “echo <Hdr$Path>” I do get a string of comma separated paths, all except the first (hdr.) being correctly starting from the root filesystem SDFS::, including one for “Global.” in which the file SWIs can be found. I have also added “Hdr:” to the Include field in the ObjAsm Dialogue box before trying the assembly. But still get no joy. |
Philip J Ludlam (50) 21 posts |
Try adding Also in the source code, it might need to read: |
Bill Antonia (2466) 130 posts |
Just tried all the permutations and combinations including adding Hdr: in the Include field but it still refuses to include the file SWIs from the <Hdr$Path> directories even though I know it is there and readable. It tries to find the file SWIs in the parent directory of my source I’m assembling, it is as if it ignores the -i directive in the command line. I’ve even tried <Hdr$Dir>. in the Include field. Any more suggestions gratefully accepted, this is bugging me. When I create a file called SWIs and put it in the place where my assembly thinks it should be, the assembler hangs and I can only abort the task. Remembered, needed to add END to the file to fix this one, dohhhhhh!!! But the GET issue is still a problem. By the way, if I add the full path to the SWIs file including the SDFS::RISCOSpi.$……. in the GET it does include the SWIs file but I get errors whilst ObjAsm is parsing the SWIs file. Dragging the “Global” directory to the Include field also had no effect, although the SWIs file is contained in that directory. |
Philip J Ludlam (50) 21 posts |
The commands: And s.source includes: My test complained about OldOpt, but that’s fixed with: What version of the compiler tools are you using? |
Bill Antonia (2466) 130 posts |
Running objasm from the command line reports it as being version 4.02 07 Sept 2014 One thing I notice though, your command line has a space between the -i and the path. when I look at the command line within the desktop tool there is no space. Tried adding one but no luck, even added one before the entry in the Include box, still didn’t work. The OldOpt error was the one that was thrown when I included a GET with the full path to SWIs. Adding an extra GET with the full path to the ListOpts file before the GET full path to the SWIs file works. What is this “do”? How does this help? Where does it go? I tried this within the command line in the !ObjAsm tool but it complained. |
Philip J Ludlam (50) 21 posts |
If you remove It looks like you need to keep doing this for every run under !ObjAsm. This might be a bug, so please raise this with ROOL. |
Bill Antonia (2466) 130 posts |
Made an edit before your reply but WHEY IT WORKS!!!!!, removed the “—desktop ^” from the command line and lo and behold it assembled without issue. Thank you, I will raise this with ROOL. |
Bill Antonia (2466) 130 posts |
ROOL provided me with a temporary fix: Go into the !ObjAsm directory and edit the Desc file. Find the line beginning “order_is” and replace the text: “—desktop " with: “-stamp " Note the spaces. Also switch off the “Work directory” option in the ObjAsm configuration menu and save back your settings. Seems there might be a bug in objasm running from the desktop. |