- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
DF2014 Talk:Installation
More info needed on Windows installation[edit]
Currently says:
- extract the archive file to a folder somewhere
- and run the game from within the folder.
I already did the first step intuitively but I am not sure how to run the game from within the folder. What file do you open? okay I figured out it is Dwarf_Fortress.exe but I think it would be good to note that, will mention on the page. 184.145.18.50 20:31, 27 February 2016 (UTC)
Needed openSUSE info[edit]
I can't find openSUSE info anywhere... --87.220.135.233 05:16, 29 April 2016 (UTC)
64bit support for Linux[edit]
Now that DF is built for amd64 much of the Linux section is unnecessary as only native libraries are needed now.
- Can confirm that the Arch Linux package is x86_64 now. 89.234.157.254 16:15, 18 October 2018 (UTC)
- I've updated the Debian-based instructions to clear up the dependency mess and only include the packages that you actually need; at some point I'll evaluate the current apt package on a new installation and see what other instructions it might need as well. It looks like the current package is v0.44.09, does anyone have experience getting it working? Tobultaran (talk) 22:58, 31 July 2019 (UTC)
libstdc++ compatibility[edit]
New installation on Debian Sid 64bit, DF 0.44.12, GCC 8.3.0. The guide works fine, but it fails with two "libs/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by /usr/lib/x86_64-linux-gnu/libGLU.so.1)". It seems to get fixed (the game starts) with a "ln -sf /usr/lib/x86_64-linux-gnu/libstdc++.so.6 libs/libstdc++.so.6" like the ones for the sound (but with -f), but doing so deletes the already existing file and I don't know what's in there, so I didn't change the main page. DD (talk) 20:19, 14 August 2019 (UTC)
- Getting rid of the DF-provided libstdc++ is something I've seen suggested lots of places; I'm surprised it isn't mentioned in the article. (And removing it is fine - you don't even need the symlink step.) The CentOS instructions do that, although in a somewhat convoluted way. I'll mention it as a general Linux compatibility fix. —Lethosor (talk) 23:33, 14 August 2019 (UTC)
- Yes, just delete it. Bundling libstdc++ is a common MISTAKE developers keep on making ever again and it almost never works, because there are so much configuration options when compiling that it is always better to use the version shipped with a distribution. --Bachsau (talk) 00:33, 15 August 2019 (UTC)