| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667 |
- <HTML>
- <BODY>
- <style>
- body { background-color: #FFFFEE; font-size: 16px; font-family: Arial;
- color: #000000; margin: 0px;
- padding-left: 0px; padding-right: 0px;
- padding-top: 0px; padding-bottom: 0px }
- H1 { padding-left: 10px; }
- P { padding-left: 10px; }
- IMG { padding-left: 0px; padding-right: 0px;
- padding-top: 0px; padding-bottom: 0px }
- A { font-size: 18px; font-family: Arial; color: #0000A0; text-decoration: none }
- A:hover { color: #000070; background: #AAffAA }
- A:active { color: #00A0A0 }
- .normal { font-size: 18px; color: #00A0A0 }
- .sub { font-size: 18px; color: #ffffdf; }
- </style>
- <P> <IMG SRC="Images/Title.png">
- </P><P> <A href="../Manual.html">Back to main page</A>
- </P><P> <b>Getting started with David Forsgren Piuva's Software Renderer</b>
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Place the library's root folder inside of a new folder.
- </P><P> This allow keeping your own projects and the "temporary" folder that's
- </P><P> used for compiling quickly outside of the library's version history.
- </P><P>
- </P><P> If using Linux, you might need to install the X11 headers.
- </P><P> If it doesn't work, your Linux distro might not have an X11 server.
- </P><P> On debian based distributions:
- </P><P> <I>sudo apt-get install libx11-dev</I>
- </P><P>
- </P><P> If using a Raspberry Pi, you can use Raspbian (Buster or newer for X11 support) or Ubuntu Mate.
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Build and run an example program on Linux:
- </P><P> * Select an SDK example and open its folder in a terminal.
- </P><P> * Give permission to execute the build script.
- </P><P> <I>chmod +x build.sh</I>
- </P><P> * Run the build script.
- </P><P> <I>./build.sh</I>
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Run regression tests on Linux:
- </P><P> * Open the source folder in a terminal and run the test script:
- </P><P> <I>chmod +x test.sh</I>
- </P><P> <I>./test.sh</I>
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Create your own Linux project
- </P><P> * Copy one of the SDK examples.
- </P><P> * Change ROOT_PATH and TEMP_DIR in your build script
- </P><P> to refer to the same locations from a new source path.
- </P><P> * Add your own external dependencies to LINKER_FLAGS within a quote
- </P><P> with -l in front of each library name.
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Creating a terminal application
- </P><P> If your application doesn't create any window, you can make it more portable
- </P><P> by replacing "WINDOW_MANAGER=X11" with "WINDOW_MANAGER=NONE".
- </P><P> This will compile with NoWindow.cpp instead of X11Window.cpp in windowManagers.
- </P><IMG SRC="Images/Border.png"><P>
- </P><P> Create your own cross-platform CodeBlocks project:
- </P><P> * Select C++ 14 with G++ from the GCC toolchain.
- </P><P> * Link with "-lm -pthread" to get standard C++ math and threading.
- </P><P> * Include all source files in the DFPSR folder or just the ones you need.
- </P><P> * Include the window wrapper and its dependencies for each target build.
- </P><P> Most platforms will be targeted using NoWindow.cpp for text only.
- </P><P> This should work with most other IDEs that support the GCC toolchain.
- </P><IMG SRC="Images/Border.png">
- </BODY>
- </HTML>
|