v50 Steam/Premium information for editors
  • 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.
This notice may be cached—the current version can be found here.

Editing v0.31:Installation

Jump to navigation Jump to search

Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.

You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "v0.31"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
{{av}}
 
{{quick download|0.31.25}}
 
 
= Download =
 
= Download =
 
__NOTOC__
 
__NOTOC__
You can always get Dwarf Fortress as [[Main:Toady One|Toady One]], the developer, released it from the [http://www.bay12games.com/dwarves/ Bay12 site] (check the top of the page).
+
You can always get Dwarf Fortress as [[Toady One]], the developer, released it from the [http://www.bay12games.com/dwarves/ Bay12 site] (check the top of the page).
  
 
You can also download the latest version here:
 
You can also download the latest version here:
Line 10: Line 8:
 
== Third-Party Packages ==
 
== Third-Party Packages ==
  
*[[Main:Lazy Newb Pack|Lazy Newb Pack]] (Windows) - the full game plus utilities and graphics sets in one big package
+
*[[Lazy Newb Pack]] (Windows Only) - the full game plus utilities and graphics sets in one big package
*[https://github.com/haesken/dftools Dwarf Fortress Auto/dftools] (GNU/Linux) - A project to auto-download/install Dwarf Fortress, Dwarf Therapist & dfhack (link not working anymore) something similar--> https://github.com/clcollins/dwarf_fortress
 
 
*[http://www.bay12forums.com/smf/index.php?topic=53180.0 Ironhand's Graphics Set] - improves the look of tiles
 
*[http://www.bay12forums.com/smf/index.php?topic=53180.0 Ironhand's Graphics Set] - improves the look of tiles
 
*[http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus' Graphic Set] - another graphics set
 
*[http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus' Graphic Set] - another graphics set
*[[Utilities#Dwarf_Therapist|Dwarf Therapist]] - Utility for managing dwarves
+
*{{L|Utilities#Dwarf_Therapist|Dwarf Therapist}} - Utility for managing dwarves
  
The Dwarf Fortress community often creates custom [[Graphics set repository|graphics sets]] and [[Tilesets|tilesets]]. They're like graphical mods that make DF look prettier or just different. A lot of people pack the game folder with the tileset installed and everything already set up, so all you have to do is extract and play. Among the most popular of these are [http://www.bay12forums.com/smf/index.php?topic=53180.0 Ironhand's Graphics Set] and [http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus' Graphic Set].
+
The Dwarf Fortress community often creates custom {{L|Graphics set repository|graphics sets}} and {{L|Tilesets|tilesets}}. They're like graphical mods that make DF look prettier or just different. A lot of people pack the game folder with the tileset installed and everything already set up, so all you have to do is extract and play. Among the most popular of these are [http://www.bay12forums.com/smf/index.php?topic=53180.0 Ironhand's Graphics Set] and [http://www.bay12forums.com/smf/index.php?topic=57557.0 Phoebus' Graphic Set].
  
There's also the (Windows only) [[Main:Lazy Newb Pack|Lazy Newb Pack]] which has several tilesets and utilities gathered together to make it easier for new players to get started and to experiment with the different tilesets. The only disadvantage to downloading LNP is that there is usually some lag time between when a new version of the game is released and when the LNP is updated to include it. So, if a new version of the game has just been released it may not be in the LNP yet.
+
There's also the (Windows only) [[Lazy Newb Pack]] which has several tilesets and utilities gathered together to make it easier for new players to get started and to experiment with the different tilesets. The only disadvantage to downloading LNP is that there is usually some lag time between when a new version of the game is released and when the LNP is updated to include it. So, if a new version of the game has just been released it may not be in the LNP yet.
  
Also see [[Utilities]] for a long list of utilities that people have created, including the incredibly useful [[Utilities#Dwarf_Therapist|Dwarf Therapist]], something that many people won't play the game without.
+
Also see {{L|Utilities}} for a long list of utilities that people have created, including the incredibly useful {{L|Utilities#Dwarf_Therapist|Dwarf Therapist}}, something that many people won't play the game without.
  
 
= Installation =
 
= Installation =
:''Also see: [[System requirements]]''
+
:''Also see: {{L|System requirements}}''
  
 
== Windows ==
 
== Windows ==
Line 37: Line 34:
 
To start the game execute the launch script "df".
 
To start the game execute the launch script "df".
  
=== OS X 10.7 Lion ===
+
Note: Users using Mac OS X 10.7 Lion you must edit this code. Open a text editor (TextEdit is standard on the Mac)
  
When first running Dwarf Fortress on 10.7 Lion, you may be startled to discover that Dwarf Fortress crashes without so much as a by-your-leave. Don't worry; Dwarf Fortress will still run on Lion. The issue lies in the libraries; they haven't changed from the ones in Snow Leopard, but their naming scheme has. The fix is a quick one. Open up the "df" launch script in a text editor of your choice (TextEdit is the default), and locate the following lines:
+
Then change
  
:export DYLD_FALLBACK_LIBRARY_PATH=${PWD}/libs<br/>
+
export DYLD_FALLBACK_LIBRARY_PATH=${PWD}/libs<br/>
:export DYLD_FALLBACK_FRAMEWORK_PATH=${PWD}/libs
+
export DYLD_FALLBACK_FRAMEWORK_PATH=${PWD}/libs
  
Change them to read as follows:
+
To
  
:export DYLD_LIBRARY_PATH=${PWD}/libs<br/>
+
export DYLD_LIBRARY_PATH=${PWD}/libs<br/>
:export DYLD_FRAMEWORK_PATH=${PWD}/libs
+
export DYLD_FRAMEWORK_PATH=${PWD}/libs
 
 
With the change, Dwarf Fortress should run normally.
 
  
 
== Linux ==
 
== Linux ==
Line 81: Line 76:
 
Dwarf Fortress is compiled for 32-bit systems, so if you're on a 32-bit system, things will be slightly easier.  If you are getting errors about missing SDL_image libraries (etc.) then you simply need to install them.  Use your distribution's package manager for this -- details will be extremely distribution-specific.  You don't need the development versions of the packages with the headers (although that won't hurt) -- you just need the runtime versions, with the actual shared libraries.
 
Dwarf Fortress is compiled for 32-bit systems, so if you're on a 32-bit system, things will be slightly easier.  If you are getting errors about missing SDL_image libraries (etc.) then you simply need to install them.  Use your distribution's package manager for this -- details will be extremely distribution-specific.  You don't need the development versions of the packages with the headers (although that won't hurt) -- you just need the runtime versions, with the actual shared libraries.
  
:On Ubuntu:
+
If you're on a 64-bit system, then things get a bit trickier.  Since DF is a 32-bit application, it needs 32-bit versions of the shared libraries.  Some Linux distributions provide these in one or more packages that you can download.  For example, in Debian, the ia32-libs package contains most of the common 32-bit libraries, including libSDL.  Unfortunately, it does ''not'' include the SDL add-on libraries such as libSDL_image and libSDL_ttf. If your distribution does not include these, then you may have to supply them manually.
:* sudo apt-get update
 
:* sudo apt-get install libsdl-image1.2 libsdl-ttf2.0-0
 
 
 
:On Ubuntu (64-bit):
 
:* sudo apt-get update
 
:* sudo apt-get install libsdl-image1.2:i386 libsdl-ttf2.0-0:i386 libgtk2.0-0:i386 libglu1-mesa:i386
 
 
 
If you're on a 64-bit system, then things get a bit trickier.  Since DF is a 32-bit application, it needs 32-bit versions of the shared libraries.  Some Linux distributions provide these in one or more packages that you can download.  For example, in Debian, the ia32-libs package contains most of the common 32-bit libraries, including libSDL.  Unfortunately, it does ''not'' include the SDL add-on libraries such as libSDL_image and libSDL_ttf. In Ubuntu, these ''are'' included. If your distribution does not include these, then you may have to supply them manually.
 
  
 
If this is the case, then the first step is to figure out where you will be putting them.  Check to see where your other 32-bit libraries are already installed; for example, on Debian, some are in /lib32 and others are in /usr/lib32.  Since libSDL is in /usr/lib32 on a Debian system, that's where we'll want to put libSDL_image and libSDL_ttf.  On other distributions, the path could be different.
 
If this is the case, then the first step is to figure out where you will be putting them.  Check to see where your other 32-bit libraries are already installed; for example, on Debian, some are in /lib32 and others are in /usr/lib32.  Since libSDL is in /usr/lib32 on a Debian system, that's where we'll want to put libSDL_image and libSDL_ttf.  On other distributions, the path could be different.
  
 
The second step is to get the 32-bit libraries.  You can typically do this by downloading them directly from your distribution's 32-bit package repository.  Again using Debian as our example, we can perform a search at http://packages.debian.org/ for files containing the word libSDL_image for the Intel x86 architecture.  This takes us to [http://packages.debian.org/search?searchon=contents&keywords=libSDL_image&mode=filename&suite=stable&arch=i386 a results page] from which we can proceed to [http://packages.debian.org/squeeze/libsdl-image1.2 the libsdl-image1.2 package page] with a list of download links arranged by architecture.  Grab the i386 package from here, and repeat this for the libSDL_ttf package, and whatever other library you are missing.  Store these package files somewhere convenient.
 
The second step is to get the 32-bit libraries.  You can typically do this by downloading them directly from your distribution's 32-bit package repository.  Again using Debian as our example, we can perform a search at http://packages.debian.org/ for files containing the word libSDL_image for the Intel x86 architecture.  This takes us to [http://packages.debian.org/search?searchon=contents&keywords=libSDL_image&mode=filename&suite=stable&arch=i386 a results page] from which we can proceed to [http://packages.debian.org/squeeze/libsdl-image1.2 the libsdl-image1.2 package page] with a list of download links arranged by architecture.  Grab the i386 package from here, and repeat this for the libSDL_ttf package, and whatever other library you are missing.  Store these package files somewhere convenient.
 
  
 
The third step is to extract the libraries from the packages and get them in the proper location.  You probably ''won't'' be able simply to install the packages using your package manager, because they are for the wrong architecture.  Instead, you'll probably have to extract them by hand.  The steps for doing this are distribution-specific, so when in doubt consult your distribution's help resources.  I'll show the steps for a .deb package.
 
The third step is to extract the libraries from the packages and get them in the proper location.  You probably ''won't'' be able simply to install the packages using your package manager, because they are for the wrong architecture.  Instead, you'll probably have to extract them by hand.  The steps for doing this are distribution-specific, so when in doubt consult your distribution's help resources.  I'll show the steps for a .deb package.
Line 143: Line 129:
  
 
Fortunately the documentation on this wiki is very detailed and extensive. You may want to start out with:
 
Fortunately the documentation on this wiki is very detailed and extensive. You may want to start out with:
* [[Tutorials]]
+
* {{L|Tutorials}}
* [[Quickstart_guide|Fortress Mode Quickstart Guide]]
+
* {{L|Quickstart_guide|Fortress Mode Quickstart Guide}}
* [[Adventure mode quick start|Adventure Mode Quickstart Guide]]
+
* {{L|Adventure mode quick start|Adventure Mode Quickstart Guide}}
  
 
Then move on to:
 
Then move on to:
* [[Dwarf fortress mode|Fortress Mode reference]]
+
* {{L|Dwarf fortress mode|Fortress Mode reference}}
* [[Adventure mode|Adventure Mode reference]]
+
* {{L|Adventure mode|Adventure Mode reference}}
 
* [[Special:Search|Searching]] the wiki
 
* [[Special:Search|Searching]] the wiki
  
 
{{Getting Started}}
 
{{Getting Started}}
 +
{{Category|Guides}}

Please note that all contributions to Dwarf Fortress Wiki are considered to be released under the GFDL & MIT (see Dwarf Fortress Wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)