Just a small update after some tests, more like note for myself. ;)
The whole process of installing Nim on FreeBSD looks that (without downloading,
decompressing, etc.):
1. Run `./build_all.sh`
2. Copy proper binaries to _/usr/local/bin_
3. Copy _lib_ directory to _/usr/local/lib/nim/_ , s
My observation related to the FreeBSD port of Nim.
Several months ago, I need to play with the development version of Nim. First I
tried to install it in FreeBSD way, by upgrading the existing port. It didn't
build. So I built Nim manually, with the standard `./build_all.sh` command. It
worked
@nealie Thank you for working on this, much appreciated.
> This probably means I have some path set wrongly somewhere in the
> configuration, or I haven't managed to modify some path search to use the
> required directory structure.
Most probably, yes.
Alas it's not that simple as to make the port I have to conform the the porting
rules, that nim breaks unfortunately. This hasn't been a problem for some time
as the port has been in good shape and has merely needed updating, but with the
move to 2.0.0, things seem to have changed a bit more.
I
Thank you for your contribution to the discussion.
I guess helloSystem?
I use Nim on a FreeBSD variant all the time and things just work. However, I
simply set my PATH to $nim/bin and don't deal with the /usr/bin stuff.
I'm working on the FreeBSD port of nim. Everything build OK and I've managed to
get it installed, but the installed compiler seems to have problems.
I'm having trouble as modules in the standard library that import other
standard library modules, but without a std/ prefix don't seem to work (the
