Mirror of forum.nim-lang.org

2126 :: Specifying compilation backend from source file

• xomachine (orginal) [2016-03-16T18:29:54+01:00] view original

  Hello dear Nim community!

  I'm looking for a way to specify compilation target (backend) for particular .nim source file. For example, there is the file describing FFI to C++ library:

  # ffi.nim
  proc someCppFunction() {.importcpp:"somenamespace::somefunction()".}
  proc someFunction*() {.exportc.} =
    someCppFunction()
  
  Run

  and the file with code that uses the interface:

  # file.nim
  # Will be compilled via
  # nim c file.nim
  from ffi import someFunction
  
  someFunction()
  Run

  Is there a way to compile first file via C++ backend and other file via C then link their .o files in usual way? I would prefer something like pragma:

  # ffi.nim
  {.target:cpp.} # Force this file to compile via C++ backend
  proc someCppFunction() {.importcpp:"somenamespace::somefunction()".}
  proc someFunction*() {.exportc.} =
    someCppFunction()
  Run

---

• Arrrrrrrrr (orginal) [2016-03-16T19:53:59+01:00] view original

  I think you can use the compile pragma here http://nim-lang.org/docs/manual.html#implementation-specific-pragmas-compile-pragma

---

• xomachine (orginal) [2016-03-16T20:53:19+01:00] view original

  The "compile" pragma is not exactly what I'm looking for. It merely adds external file to compilation process. But this file has to be written manually. So this pragma does not allow to use Nims metaprogramming features to generate FFI like that.

---