8000 Filepaths in main files behave differently to filepaths in included files · Issue #20 · VitorVilela7/UberASMTool · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Filepaths in main files behave differently to filepaths in included files #20

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DiskPoppy opened this issue May 14, 2021 · 2 comments

Comments

@DiskPoppy
Copy link

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.

@VitorVilela7
Copy link
Owner

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.

@DiskPoppy
Copy link
Author
DiskPoppy commented Apr 7, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0