Building Dolphin on Linux: Difference between revisions

Jump to navigation Jump to search
Line 15: Line 15:
If you run a distribution without aptitude, see the build dependencies in addendum A for a list of packages you'll need to install.
If you run a distribution without aptitude, see the build dependencies in addendum A for a list of packages you'll need to install.


==Step 2 - Get the dolphin repository==
==Step 2 - Get the Dolphin repository==
Install git if you don't have this already.<br>
Install git if you don't have this already.<br>
<code>sudo apt-get install git</code>
<code>sudo apt-get install git</code>
Line 27: Line 27:
Later, if you wish to update your local copy you run following command and proceed with the following steps.<br>
Later, if you wish to update your local copy you run following command and proceed with the following steps.<br>
<code>git pull origin</code>
<code>git pull origin</code>
==Step 3 - Building Dolphin==
Create a build subdirectory, and change into it. <br>
<code>mkdir Build && cd Build</code>
Configure the build.<br>
<code>cmake ..</code>
You may also want to change the install prefix by adding "-D CMAKE_INSTALL_PREFIX=/new/path". Note that this path does not need to be absolute. cmake will complete it to its absolute equivalent. The default prefix is "/usr". This means that the executable will be installed as "/usr/bin/dolphin-emu", the plugins will be installed into "/usr/lib/dolphin-emu", and the shared data files will be installed into "/usr/share/dolphin-emu".<br>
<br>
From here build and install in the standard make way.<br>
<code>make && make install</code>
Note that you may need superuser privileges for the last command.<br>
<br>
If you must insist on having the "local" build setup from the deprecated scons build you can configure the build with the following command.<br>
<code>cmake -Dbindir=../Binary/Linux -Ddatadir=../Binary/Linux  ..</code>


==Addendum A - dependencies==
==Addendum A - dependencies==