On win64, versions 1.4 and 1.5 at least, I can execute an include -I with -I"." for current dir, and it works fine. Finds include files. If I put anything else there, such as -I"C:\Users\username\git\project.git\source" I get an often confusing error message. It doesn't help if I omit the drive letter or reverse my slashes to unix style.
The assembly file doesn't need to include anything from source for this to happen, simply by including this -I it breaks and I can't sort out why. It's entirely possible I'm misusing -I but the error message isn't directing me towards the cause. I have also included longer files where the file name in the error is truncated, not at the ends, but in the middle, and placed in this error message. I'm having trouble reproing that 3rd case with my example at the moment. Let me know if I can provide any more examples or assist in finding the cause in any way, thanks!
EdouardBERGE
commented
2 years ago
On win64, versions 1.4 and 1.5 at least, I can execute an include
-Iwith-I"."for current dir, and it works fine. Finds include files. If I put anything else there, such as -I"C:\Users\username\git\project.git\source" I get an often confusing error message. It doesn't help if I omit the drive letter or reverse my slashes to unix style.Examples:
Result:
Cannot find file [≡╛v ☺]Result:
Cannot find file [emulator_main]The assembly file doesn't need to include anything from source for this to happen, simply by including this
-Iit breaks and I can't sort out why. It's entirely possible I'm misusing-Ibut the error message isn't directing me towards the cause. I have also included longer files where the file name in the error is truncated, not at the ends, but in the middle, and placed in this error message. I'm having trouble reproing that 3rd case with my example at the moment. Let me know if I can provide any more examples or assist in finding the cause in any way, thanks!Environment: Windows 10 x64 RASM 1.5 x64