{"assets":[{"original":"http:\/\/www.ludumdare.com\/compo\/wp-content\/uploads\/2013\/04\/MPH_Computer-550x368.gif","local":"\/data\/posts\/2013\/04\/840e86580d735959a35549f4c18ff90d.gif"},{"original":"http:\/\/www.ludumdare.com\/compo\/wp-content\/uploads\/2013\/04\/LDOSX1-300x108.png","local":"\/data\/posts\/2013\/04\/426c36c260f39327978e0fb04a8e6060.png"},{"original":"http:\/\/www.ludumdare.com\/compo\/wp-content\/uploads\/2013\/04\/LDOSX2-300x83.png","local":"\/data\/posts\/2013\/04\/63f7ec1e26e969ff50bdacfa4a799d4f.png"}],"author_link":"author\/sko\/","author_name":"Avant-Marde","cat":"LD #26","categories":["LD #26"],"comments":[],"epoch":1366805460,"event":"LD26","likes":9,"metadata":{"p_key":"80224","p_author":"Avant-Marde","p_authorkey":"0","p_urlkey":"289234","p_title":"Holy trinity of SFML 2.0 (how to set up)","p_cat":"LD #26","p_event":"LD26","p_time":"1366805460","p_likes":"9","p_comments":"0","p_status":"WAYBACK","us_key":null,"us_name":null,"us_username":null,"event_start":"1366934400","event_key":"16","event_name":"LD26"},"source_url":"2013\/04\/24\/holy-trinity-of-sfml-2-0-how-to-set-up\/","text":"

Cheers!<\/span><\/strong> I have now successfully set up SFML 2.0<\/strong> (for C++<\/em>) to compile for\u00a0OS X<\/strong>,\u00a0Linux<\/strong> and\u00a0Windows<\/strong>! This confirms my main framework for programming. Initially, though, I was as confused as a\u00a0pOtaToR<\/span><\/strong>.<\/em><\/p>\n

\"POTATOR\"<\/a><\/p>\n

Let me explain what I went through, and let me see if I can help you too, in case you are also having problems setting SFML 2.0 up in a cross-platform environment!<\/p>\n

<\/span><\/p>\n

So, I have two laptops for this purpose. One is a Mac<\/em> and, naturally, what I use to compile for OS X<\/em>. I am using Xcode 4.6.2<\/strong>, to which I updated just two days ago or so. The other laptop is running, now good and old, Ubuntu 10.10 Maverick Meerkat<\/strong>. This is where dual cross-compiling magic happens; I natively compile the\u00a0Linux<\/em>\u00a0executable here, of course, using G++<\/em>, but also the\u00a0Windows<\/em> version, using MinGW<\/em>. My Linux IDE is\u00a0Code::Blocks<\/strong>. I will be working on the Mac, only moving on to this laptop when I need to compile for the other two systems. The Windows version also runs fine in\u00a0Wine<\/strong>.\n<\/strong><\/p>\n

I did have some trouble here and there when it came to setting it up for the various systems, and I thought I\u2019d briefly mention them in case anybody else wishes to work with a multi-platform SFML 2.0 setup and is running into problems similar to those that I have had.<\/p>\n

\u00a0<\/p>\n

OS X<\/h2>\n

For OS X, I first downloaded the SFML 2.0 OS X release candidate<\/a>\u00a0and\u00a0tried setting up the frameworks and the Xcode templates. This all seemed unsuccessful, initially. I never got the templates properly working in the end either, but I didn\u2019t need them. I set up an empty project instead, and started setting it up.<\/p>\n

I never needed to manually set, in the project\u2019s\u00a0build phases<\/em>, any frameworks to link with, because I decided to do it with linker flags*<\/em> instead,\u00a0but if linking errors crop up, I would suggesting manually dragging the SFML frameworks here. The build phase settings are found by clicking the project name at the top of the Xcode window\u2019s left file hierarchy bar (shown by pressing cmd+1<\/em> if it is not visible), and then the target with the same name. At the top of the main box will be a few tabs, and one of them is for the build phases.<\/p>\n

\"Xcode<\/a>

Ignore the AngelScript target \u2013 it has nothing to do with SFML. I just happened to be testing AS in the same project.<\/p><\/div>\n

What I did have to do, however, were two things, located in the build settings<\/em>. Those of the project, above the targets in the white middle column visible in the above picture, rather than those of any specific target. If your only target is the application itself, though, and you don\u2019t have a second one like my AS one here, it doesn\u2019t matter, though.<\/p>\n

    \n
  1. *This asterisk refers back to those aforementioned\u00a0linker flags<\/strong>. Instead of adding the frameworks to the project\u2019s build settings, I added the following line to the\u00a0other linker flags<\/em>:\n
    -framework sfml-system\u00a0-framework sfml-window\u00a0-framework sfml-graphics<\/pre>\n
    If audio or networking or anything is needed, add those as well. The\u00a0other linker flags\u00a0<\/em>are found as such:<\/p>\n
    \"Setting<\/a>
    Setting linker flags in Xcode<\/p><\/div>\n
    I also had to manually set the path to the global frameworks\u2019 folder, under the framework search paths<\/em>, for some reason, which Google helped me find out. I set it to\u00a0\/Library\/Frameworks<\/em> and I did it in the application\u2019s target, but the project\u2019s global build settings will work just fine too.<\/p>\n
    \"Setting<\/a>
    Setting the frameworks\u2019 search path<\/p><\/div><\/p><\/li>\n
  2. Then I had to pick compilers\u00a0without C++11 support<\/em>\u00a0because the RC of SFML has been compiled without such support and is incompatible with a program compiled with it, which would give errors.\n
    \"Setting<\/a>
    Setting non-C++11 compiler<\/p><\/div><\/p><\/li>\n<\/ol>\n
    That was it, and I had it working under\u00a0OS X<\/strong>!<\/p>\n
    \u00a0<\/p>\n
    Linux<\/h2>\n
    For Linux, I tried doing things in various ways until I eventually ended up compiling SFML myself using Make, following this wonderful tutorial for Ubuntu<\/a> written by a certain\u00a0Xandier314<\/em> in 2011. This means that I did not download the release candidate for Linux, but the latest development snapshot<\/a> found at the very top of the download page.<\/p>\n
    As the article itself says, the tutorial focuses on Ubuntu specifically, but should be applicable to most Linux distributions with the exception of package management which might work differently in order to acquire the prerequisities<\/em> needed to compile SFML. Surely any programming Linux user would already know how to do this on their specific system. If not, Google is your very best friend.<\/p>\n
    Having followed this didn\u2019t end my problems right away, though. Compiling or linking still didn\u2019t work properly even after installing everything. The solution, however, was simple, even though it did require a little searching on my part.<\/p>\n