-
Notifications
You must be signed in to change notification settings - Fork 0
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
Build from source code #15
Comments
Yes, it needs the path to LLVM in order to build it. For example,
On Windows, this would be a different path, and would depend on how to obtained your copy of llvm 18.1. Also as a side note, it is not in a usable state yet. Only the support for arm64 macOS is finished at the moment, although I just added bare-bones support for unfinished platforms in the latest commits 7c46f57 and 16f4867. So it is possible to use it on Windows, it just requires manual linking (with mingw64 for example) and doesn't support complicated C ABI interoperability yet (only basic types can be passed to C functions). The only parts that are mostly stable right now are simple single file programs using the C standard library. And being the early development days, everything is still subject to change. Some features are having their designs revisited too, so even if something works it might not be final. These include but are not limited to: structures, memory management, multi-file programs, integer overflow behavior, primitive type names, syntax used and more. Here some example programs in the current iteration though:
|
@Spoiledpay On Windows, please use MSYS2. It will be very straight forward. |
Hello! I hope you are well!
I tried and I don't even know if I did it the right way. I downloaded the new Adept 3.x compiler. I installed the Rustc compiler.
I used Cargo Build and it didn't compile, I imagine something is missing for completion. Something related to LLVM.
The text was updated successfully, but these errors were encountered: