Last modified by Soeren Domroes on 2025/01/30 12:18

From version 7.1
edited by stu122612
on 2020/04/18 08:40
Change comment: There is no comment for this version
To version 6.1
edited by stu120505
on 2020/04/03 00:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.stu122612
1 +XWiki.stu120505
Content
... ... @@ -2,7 +2,7 @@
2 2  
3 3  The source code lies and building happens inside the folder called {{code language="none"}}pinballProject{{/code}}. For a fresh build, you need a not too old version of {{code language="none"}}make{{/code}}, a C++ compiler (we only tested {{code language="none"}}g++{{/code}}), an internet connection (for downloading the Kieler Compiler), the libraries {{code language="none"}}wiringPi{{/code}} and {{code language="none"}}opencv{{/code}} as well as the command-line tools [[mega-cmd>>url:https://mega.nz/cmd||shape="rect"]] and {{code language="none"}}python2{{/code}}. The tool for mega.nz (and also {{code language="none"}}python2{{/code}}) can be omitted (see below on how to compile without them), everything else except for {{code language="none"}}opencv{{/code}} comes pre-installed with Raspbian. For {{code language="none"}}opencv{{/code}} you need a 4.x version, 4.2.0 ought to work for example. Make sure to enable the option that the entries for {{code language="none"}}pkg-config{{/code}} get configured. It can be built from source on the Raspberry Pi in a few hours, make sure not to use too many threads for compilation because of limited RAM, also perhaps increase the swap.
4 4  
5 -With all the prerequisites met, you can use the {{code language="none"}}Makefile{{/code}} to build everything.
5 +With all the pre-requisits met, you can use the {{code language="none"}}Makefile{{/code}} to build everything.
6 6  
7 7  (% class="wrapped" %)
8 8  |=(((
... ... @@ -189,6 +189,6 @@
189 189  while paused, advance by one frame
190 190  )))
191 191  
192 -If you re-calibrate the coordinate system on the Pi, you might want to transfer the config file for the coordinate system (however there is nothing really depending on the coordinate transformation being correct inside the image detection anyways).
192 +If you recalibrate the coordinate system on the Pi, you might want to transfer the config file for the coordinate system (however there is nothing really depending on the coordinate transformation being correct inside the image detection anyways).
193 193  
194 194  The ability to compiler the whole project off the Pi allows for catching type errors etc. more quickly, since compilation on the Pi tends to be a lot slower and also there‘s not the option to use the Kieler IDE on it (so you’d maybe also need to transfer the code). The {{code language="none"}}pinballProject{{/code}} folder contains an Eclipse project that can be used with Kieler. Building from the Kieler IDE still happens by invoking the Makefile. There should be a build configuration using {{code language="none"}}make{{/code}} included in the project. (I’m only specifying “should” since we didn’t really test the experience of importing the project into a workspace too often.)
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -73072936
1 +73072935
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/73072936/Dependencies and Compilation
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/PP18/pages/73072935/Dependencies and Compilation