Differences

This shows you the differences between two versions of the page.

--- proton:linux_setup [2023/06/08 09:08] – [Compiling and running RTBareBones] seth
+++ proton:linux_setup [2023/06/08 13:21] (current) – [IDEs] seth
@@ Line 1: / Line 1: @@
 ==== Compiling the examples for Linux ====
-In order to build the examples on Linux you first need some dependencies installed on your system. All of the needed dependencies are common in Linux distributions so you'll probably find everything needed through your distribution's package manager. The name of the packages vary slightly from distribution to another so you'll might need to search for the specific names a little.
+This page will tell you how to get some examples compiling under Linux.  I'm using the latest Ubuntu as of June 8th, 2023 for this test.  The binaries should run both under the desktop, or from bash without the desktop environment running.
-The build scripts available for Linux use [[http://www.cmake.org/|cmake]] so you have to have that installed. In addition you need a bunch of other usual build tools like gcc, libc, make and possibly others. The Linux version uses SDL so you'll also need some development packages for SDL2. It's usually called SDL2-devel and in order to hear sounds you'll also need SDL2_mixer-devel. This is not a complete list of the dependencies so you might need to try if the building succeeds and if not then install some more dependencies. Sometimes the build process outputs a sane error message that tells what is missing, sometimes it doesn't. Good luck :-P
+The examples may have weird window sizes and in non-desktop environments things like mouse cursor movement won't work.
 ==== Grabbing Proton SDK ====
-Ok, this was tested on a Raspberry Pi with Stretch, but normal linux distributions should be roughly the same.
+First, let's install some tools and libraries we need in case you don't have them.
-First, let's install some tools in case you don't have them.
 <code bash>
 sudo apt install git build-essential libffi-dev zlib1g-dev libssl-dev
@@ Line 120: / Line 118: @@
 You basically only have to run cmake manually once per build directory. After that you can just run make. If the CMakeLists.txt file has been changed it is noticed by the build scripts and cmake is run automatically with the same parameters as it was run the first time.
-==== Command line arguments ====
-**Note 7/28/2018:**  I don't think any of this applies anymore since I switched the linux builds to use the normal SDL/SDL2Main.cpp file as a base? -Seth
-The Linux versions of the examples accept a few command line arguments. You can choose the video mode and emulated environment (e.g. iOS, Android,...) from a predefined set of presets. You can get a list of the available modes by running any of the examples with option ''-l''.
-<code bash>
-[user@localhost]$ ./RTSimpleApp -l
-Available video modes:
-Windows
-Windows Wide
-OSX
-OSX Wide
-Linux
-Linux Wide
-iPhone
-iPhone Landscape
-[...]
-</code>
-You can choose any of these modes by giving the name of it as an argument to the program. For example testing how an application might look on an iPad you can command:
-<code bash>
-./RTSimpleApp "iPad Landscape"
-</code>
-Note that you need to enclose modes with spaces between quotes.
 ==== IDEs ====
-All of the tools mentioned on this page work from the command line. It means that no IDE is chosen for you beforehand. You are free to use any editor or IDE you like, be it emacs or vi or something more sophisticated.
+I've gotten things to work ok with VScode, I use it remotely on my Windows machine and ssh into the linux box.  I set the project dir to "proton/RTBareBones" for example, and with the CMake Tools active I can specify the linux/CMakeLists.txt file to build and debug with.
-As a personal preference I'm using QtCreator. It has a nice built-in importer for cmake projects. Although QtCreator is mainly meant for Qt development it's a great IDE for any C++ development. You can open the CMakeLists.txt file with QtCreator and it automatically imports the project in to the IDE. You might need to set some paths or such in the project settings but it's relatively easy to get the building work with Ctrl+B and running with Ctrl+R. QtCreator also has a great UI for debugger.
-You can set multiple run configurations so you can run the applications with different command line arguments for example - perhaps setting a different window resolution for each configuration.
+The only problem is I can't get breakpoints in ../proton/shared files to hit, even though I've added the folder to the project and played with source mapping, hrmph.