This isn't true... the linker simply needs to know where to find the shared
library.
Depending on what compiler / linker you're using - the syntax for providing a
path to linked libraries can vary.
If you're using gcc for instance, you can set the LIBRARY_PATH env variable or
by specifying pat
It is installed, but it has to be in the same directory as the rest, else it
does not appear to be recognized. That makes sense, of course. It's as you
describe now ... and I probably should have upgraded to 0.19 earlier.
When sdl.nim is missing (package not installed) you should get an error at
compile time. When a dll is missing, you should get an error when you launch
your executable.
Okay, so apparently I've mixed up example files ... and it's not the dll that's
missing, but the package. I've figured it out by looking at the tests in
nim/tests/.../sdl. I saw "import sdl" and went "oh" That doesn't explain
why i have the dll problem with csfml, but at least this is probab
Ah okay, so apparently the sdl.nim is **required** to work, and it is not
actually asking for the dll (like it did in the old version) but actually asks
for sdl.NIM ... man ...
Greetings. I don't know why it is not working.
I have updated to the latest nim. I have made sure that I have the correct dll
installed, which is the 64bit version. I have placed the dll everywhere where
it might make sense, including system32 and nimbin and, of course, the local
directory.
Wh
