Closed wenghongquan closed 2 years ago
This has all been automated, don't touch this code. You need to patch compiler.ini and run the appropriate steps which I forgot. But then I don't want to review your diff either (it would be much too risky, sorry!) so I have to do myself. Ping me again in 4 days if I haven't done it by then.
This has all been automated, don't touch this code. You need to patch compiler.ini and run the appropriate steps which I forgot. But then I don't want to review your diff either (it would be much too risky, sorry!) so I have to do myself. Ping me again in 4 days if I haven't done it by then.
That is great.
This has all been automated, don't touch this code. You need to patch compiler.ini and run the appropriate steps which I forgot. But then I don't want to review your diff either (it would be much too risky, sorry!) so I have to do myself. Ping me again in 4 days if I haven't done it by then.
hey Araq, have you finished it?
Sorry, please I'll do it this weekend. If not ping me again on Monday.
update?
hi @Araq , Do you have any problem during the process?
Hi @Araq , if these files need to be automatically generated, you can refer to https://wiki.debian.org/LoongArch/sbuildQEMU to build the environment. If Nim wants to successfully support loong64, we need your help. Nim build in debian status
Well, Loongarch64
has been supported by https://github.com/nim-lang/csources_v2, which has been used for Nim 2.0
Wow, very good! About 1.6.14 version in debian, is there a good way to push it forward? https://buildd.debian.org/status/package.php?p=nim&suite=sid
Perhaps, you can tell me a method how to automate the generation of the files in v1 version
Suit for devel (nim-lang/Nim#19223) Add cpu loongarch64 in build.sh, makefile and c_code for build success in loongarch PC.
All I have done is:
please review it, thanks!