Mirror of forum.nim-lang.org

844 :: What toolchain are YOU using for Nim development?

• jgoodgive (orginal) [2015-02-08T12:44:48+01:00] view original

  I think it could be interesting to know what others are using for what type of development.

  • Editor: Aporia, emacs, visual studio or sublime text...
  • Code completion, go to definition tools/plugins?
  • Compiler: gcc, vcc (cl), 64/32 bit, clang?
  • Debugger, watcher: Visual studio, linux black magic, gdb ?
  • Memviewer: VS, other?

  Any problem setting up your environment that others might want to know about?

---

• jgoodgive (orginal) [2015-02-08T12:50:40+01:00] view original

  I began using aporia but due to doing some C coding in emacs is currently trying the emacs nim-mode.el, which has promise but also some issues for the version of emacs I am using in windows. But as I want to try some game development and need to handle memory manually I want to debug using VS or a similar tool, meaning that I need to either use a tool like visual-nimrod or manage to compile using VCC and create PDB information with enough debug comments so that I can read and understand what nim code created what c code. Neither of my environments are really working but all are showing promise.

  -Edior: Emacs

  -plugin: nim-mode.el

  -compiler:gcc (playing around with vcc)

  -debugger: nothing that really works atm.

  -mem view: ?

---

• filwit (orginal) [2015-02-08T14:07:08+01:00] view original

  I use Kate on linux with my NimKate. I use Notepad++ on Windows because I don't use it as much and I can adjust colors easy.

---

• LeuGim (orginal) [2015-02-08T14:15:49+01:00] view original

  Editor: EditPlus (for Windows), compiler: gcc (MinGW), memview/debugger: I was using once Delphi...

---

• DarkBlue (orginal) [2015-02-08T14:35:50+01:00] view original

  Kate with NimKate on openSuse13.2

---

• Varriount (orginal) [2015-02-08T16:50:30+01:00] view original

  Sublime Text 2 with NimLime on Windows, using Mingw-w64

---

• Orion (orginal) [2015-02-08T18:03:50+01:00] view original

  Sublime Text 2 / 3 with NimLime on Windows (mingw) and OS X (clang).

---

• didlybom (orginal) [2015-02-08T20:58:06+01:00] view original

  I'm using Atom as my editor, with the language-nimrod package which gives you basic syntax highlighting and not much more.

  To compile I am using the provided MinGW compiler on windows and the VxWorks gcc cross-compiler to generate PowerPC VxWorks RTP applications (small test apps for now, nothing serious).

---

• OderWat (orginal) [2015-02-08T22:48:11+01:00] view original

  I used mainly "CodeRunner" on Mac with my own adopted syntax / color and compiler script but moved on, because I need to get an setup which can be replicated on linux and windows.

  Sublime Text 3 with NimLime on Mac OS using clang (mostly).

  Debugging was not yet a focus. I occasionally use Bit-Slicer for peeking live into memory (advertised as game-trainer it can to a lot more important stuff).

  I tried to get tinycc runnig (with --run) to use Nim for scripting which partially succeeded but I ditched it after I found that I am wasting to much time for this right now :)

---

• dom96 (orginal) [2015-02-09T01:04:31+01:00] view original

  Still rocking good old Aporia :)

  Compiler: gcc

  Debugger: echo and occasionally gdb

---

• jboy (orginal) [2015-02-09T03:16:14+01:00] view original

  I'm old-fashioned and lazy: Vim (with Python syntax highlighting triggered by a .nim filename suffix) on Linux with GCC & GDB. No problems getting anything working.

  I know there's a Vim plugin on Github, but like I said, I'm lazy...

---

• AxBen (orginal) [2015-02-09T09:51:33+01:00] view original

  GVim with my own syntax file on Windows, compiling with Mingw-w64.

---

• perturbation2 (orginal) [2015-02-09T16:30:09+01:00] view original

  Editor: vim + tmux with the nimrod.vim plugin. I used to use Aporia, but since I use vim for everything else, I drifted back into using that for Nim as well.

  Compiler: GCC

  Debugger: GDB + valgrind.

  OS: Linux (Debian Wheezy variant)

---

• Vladar (orginal) [2015-02-10T10:26:30+01:00] view original

  Editor: gvim + nimrod.vim plugin

  Compiler: gcc, mingw under wine

  Debugger: echo

  OS: CrunchBang/Debian Jessie

---

• def (orginal) [2015-02-10T11:52:02+01:00] view original

  Editor: vim + nimrod.vim

  Compiler: gcc, clang (often faster compile and binary) and tcc (so much faster to compile)

  Debugger: echo, gdb

  OS: Gentoo, Archlinux, Debian

---

• zio_tom78 (orginal) [2015-02-10T11:55:26+01:00] view original

  Editor: emacs + nimrod-mode

  Compiler: gcc

  Debugger: echo, stack traces, tests

  OS: Xubuntu, OpenBSD, CentOS

---

• akiradeveloper (orginal) [2015-02-11T10:05:43+01:00] view original

  Editor: Vim + tmux, Compiler: gcc, Debugger: echo, OS: Debian

  neocomlcache plugin doesn't get along with nimrod.vim so I disable it while writing Nim

---

• Araq (orginal) [2015-02-11T10:32:55+01:00] view original

  Since most people list echo here, let me remind you that writeStackTrace is also invaluable for debugging as it answers the question "why and in which context is this called?". Traditional debuggers can show stack traces too of course, but when you debug non-toy examples, you need conditional breakpoints which tend to not work very well. An if cond: writeStackTrace() is far more effective.

---