Replies: 1 comment 1 reply
-
Oh right, so you're building a modified version of the executable? I was ready to give you some sample code, but then I realized that the abstraction layer I'm using for the file system doesn't allow for non-existent files right now... So that might need some work! In case you're just using the official executable, you can pass multiple file names as arguments (e.g. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
A thought I has was: What if there was a way to embed the text of your cpu rules inside of the binary so that end users wouldn't have to know about including a file defining the cpu?
This could maybe be a part of the process of building customasm or something. I have a little knowledge of the way Rust and Cargo works, so maybe as a part of the "build script" if a certain extra file exists (ie.
cpu_def.rs
) it enables "embedded mode". And thencpu_def.rs
includes a string variable that includes the contents of your cpu definition which gets automatically processed at the beginning of all customasm invocations.Beta Was this translation helpful? Give feedback.
All reactions