Library construction and use

[chen4s666]

Hi, I've been trying to build or import libraries recently. But I'm still having trouble importing the standard library correctly.
I am currently using a windows computer system, I want to compile and build the library on windows in the whole process, and then put the compiled files to run on linux system.
I have tried to go into the libs folder and compile with the 'cargo build --release' command, which produces either '.a 'or'.o 'files, but when I use the library files and try to compile with my st project files, it doesn't work.
I also tried to compile the scripts in "#576" and run the script using "git bash here "on windows, but it didn't work properly either.
The following error occurred

$ ./build.sh --build --release --package
Build starting
-----------------------------------
Finished 'release' profile [optimized] target(s) in 0.33s
-----------------------------------
Build done
Build starting
-----------------------------------
Finished 'release' profile [optimized] target(s) in 0.33s
-----------------------------------
Build done
lld-link: warning: ignoring unknown argument '--whole-archive'
lld-link: warning: ignoring unknown argument '--no-whole-archive'
lld-link: error: could not open 'iec61131std.lib': no such file or directory
lld-link: error: could not open 'm.lib': no such file or directory
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Can you help me with this problem? Thank you very much.
The above attempts are based on the master branch version, although I am actually still using release 0.2.0.
In addition, I would like to ask about the subsequent release version plan.

[ghaith]

Hello @chen4s666,

You are trying to build a linux library on windows, the build script for the library assumes it's being built for a linux system.
The library can work for a windows system but it has not been tested.
You can however build the library for linux from a windows system (which is as I understand your goal here)
To do this you can use the --target argument. An modern intel/amd system will have the architecture x86_64-unknown-linux-gnu so you can build with --target=x86_64-unknown-gnu a 64bit arm system (like the raspberry pi 5) is aarch64-unknown-linux-gnu. To build from windows, it might be that you would need a sysroot in addition the compiler, this is basically a copy of all your system libraries so that the linker can access the system libraries we need such as libc the easiest way to get a sysroot is to copy the / directory from a running target locally. You can then pass the location of the sysroot with the --sysroot flag I'm not sure if we included this flag in the build script, but it's usually passed to a compiler/linker with --sysroot so you can update the build script if needed.
For reference, take a look at how we call the script in our build pipeline under .github/workflow

Hope this helps

[chen4s666]

Thank you for your answer, which is of some help to me.
And I have another idea. Since LLVM can generate IR code, can we increase the parsing of IR code? This way we can compile the library into IR code, it can be used like a library, and it can be cross-platform.

[mhasel]

I'm not sure I understand your idea correctly, so feel free to highlight any errors. What do you mean with increase the parsing of IR code?
Anyhow, it is already possible to compile to IR with rusty by passing --ir to the compiler - it will emit .ll files (on master, the file ending might still be different on 0.2). You would then still have to compile the resulting IR further with a llvm-compatible backend of your choice for your target platform.

[chen4s666]

For example, I can use the following command to generate IR code.
For the sake of presentation, I gave the file path freely.It is better to use the '--bc' parameter to generate the '.bc 'file.
rustyc.exe --ir D:\rusty\libs\stdlib\iec61131-st\*.st -o D:\stlib.ll
The 'stlib.ll' file I generate at this point is a platform-independent intermediate file that can be used as a library when I need to use it and recompiled into code for the target platform.
rustyc.exe --target=aarch64-unknown-linux-gnu D:\test.st --include D:\rusty\libs\stdlib\iec61131-st\*.st -L D:\ -l stlib