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: | ||
− | |||
− | |||
= Download = | = Download = | ||
__NOTOC__ | __NOTOC__ | ||
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 | + | *[[Main:Lazy Newb Pack|Lazy Newb Pack]] (Windows Only) - the full game plus utilities and graphics sets in one big package |
− | |||
*[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 | ||
Line 37: | Line 34: | ||
To start the game execute the launch script "df". | To start the game execute the launch script "df". | ||
− | + | Note: Users using Mac OS X 10.7 Lion you must edit this code. Open a text editor (TextEdit is standard on the Mac) | |
− | + | Then change | |
− | + | export DYLD_FALLBACK_LIBRARY_PATH=${PWD}/libs<br/> | |
− | + | export DYLD_FALLBACK_FRAMEWORK_PATH=${PWD}/libs | |
− | + | To | |
− | + | export DYLD_LIBRARY_PATH=${PWD}/libs<br/> | |
− | + | export DYLD_FRAMEWORK_PATH=${PWD}/libs | |
− | |||
− | |||
== 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. | ||
− | + | 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. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | 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 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 153: | Line 139: | ||
{{Getting Started}} | {{Getting Started}} | ||
+ | {{Category|Guides}} |