Mirror of forum.nim-lang.org

4162 :: Error: system module needs: copyString

• markprocess (orginal) [2018-08-27T11:34:53+02:00] view original

  How do I satisfy the need for copyString when using --os:standalone --gc:none ?

  Thanks, Mark

---

• DeletedUser (orginal) [2018-08-27T12:06:35+02:00] view original

  I think you need deepCopy

---

• markprocess (orginal) [2018-08-27T13:54:47+02:00] view original

  If I find an implementation of deepCopy, do I just add a copy of it to my source file?

---

• coffeepot (orginal) [2018-08-29T11:15:19+02:00] view original

  deepCopy should be available everywhere, you don't need to copy the implementation to your source.

---

• Araq (orginal) [2018-08-29T12:36:39+02:00] view original

  https://github.com/nim-lang/Nim/tree/devel/tests/manyloc/standalone shows how to do it.

---

• markprocess (orginal) [2018-09-07T03:21:19+02:00] view original

  I added

  var s = "a" & "b"

  to tests/manyloc/standalone/barebone.nim

  and received "system module needs: copyString"

  How do I satisfy this requirement? Thanks, Mark.

---

• Araq (orginal) [2018-09-07T08:40:22+02:00] view original

  String concats do allocate, --os:standalone --gc:none is for developing operating systems. When you develop an operating system, you have to have your own memory manager.

---

• markprocess (orginal) [2018-09-07T09:40:18+02:00] view original

  Sorry - I neglected to mention that I am using --app:staticlib and linking the the generated c code to a host program that provides services by exporting procs and the nim code uses importc to call the services. One service is to broadcast a string on bluetooth, hence the desire to concatenate strings.

  So, I'm not developing an operating system - maybe I shoudn't use os:standalonegc:none?

  There is no os - the host program does not use one.

---

• Araq (orginal) [2018-09-07T10:40:59+02:00] view original

  Well --app:staticlib doesn't require os:standalone nor gc:none as far as I'm aware.

---

• markprocess (orginal) [2018-09-08T05:57:23+02:00] view original

  I went back to --app:staticlib --os:standalone --gc:none and simplified my project to just qemu for the purpose of getting strings to work: https://github.com/markprocess/nim-ultibo-prototype

  Without standalone, I get the following things like stdio.h in stdlib_system.c, which I don't want:

  /* Generated by Nim Compiler v0.18.1 */
  /*   (c) 2018 Andreas Rumpf */
  /* The generated code is subject to the original license. */
  /* Compiled for: Linux, amd64, gcc */
  /* Command for C compiler:
     gcc -c  -w -O3 -fno-strict-aliasing  -I'/root/.choosenim/toolchains/nim-#devel/lib' -o /root/.cache/nim/nimmain_r/stdlib_system.c.o /root/.cache/nim/nimmain_r/stdlib_system.c */
  #define NIM_NEW_MANGLING_RULES
  #define NIM_INTBITS 64
  
  #include "nimbase.h"
  #include <sys/mman.h>
  #include <stdio.h>
  #include <stdlib.h>
  #include <string.h>
  #include <setjmp.h>
  #include <signal.h>
  

---

• Araq (orginal) [2018-09-08T08:05:01+02:00] view original

  Without standalone, I get the following things like stdio.h in stdlib_system.c, which I don't want:

  "stdio.h" doesn't prevent --app:staticlib.

---

• markprocess (orginal) [2018-09-08T08:56:31+02:00] view original

  I updated https://github.com/markprocess/nim-ultibo-prototype but I get

  stdlib_system.c:8:22: fatal error: sys/mman.h: No such file or directory
  

---

• markprocess (orginal) [2018-09-08T20:20:47+02:00] view original

  https://github.com/markprocess/nim-ultibo-prototype/issues/1

---