Filepaths in main files behave differently to filepaths in included files · Issue #20 · VitorVilela7/UberASMTool · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the files included directly from the list, filepaths (in insrc, incbin, table, %prot_source, etc.) are treated as relative to UberASMTool.exe. However, in the incsrc'd files, the filepaths are treated as relative to the file's location.
The text was updated successfully, but these errors were encountered:
Sorry for the late question, but do you have any example in what potential problems this can have exactly? If I remember correctly, Asar lets you configure which folders to look for the ASM files, but I don't remember if this misbehavior is intentional or if it's something that is caused by UberASM Tool internals.
From what I can remember it just caused confusion, but it was solved I think by replacing incbin "../<file>" with incbin "/../<file>", same with incsrc, in the prot_file and prot_source macros in macro_library.asm. However, I'm not sure as as of 1.4 and 1.5 incsrc, incbin, table appear to work as expected now, but I'm not using the prot macros anymore.
In the files included directly from the list, filepaths (in insrc, incbin, table, %prot_source, etc.) are treated as relative to UberASMTool.exe. However, in the incsrc'd files, the filepaths are treated as relative to the file's location.
The text was updated successfully, but these errors were encountered: