Differences

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

Link to this comparison view

Both sides previous revision Previous revision
manual:chapter1:buildfromsource [2018/01/03 12:24]
claudio [Building the Desktop simulator]
manual:chapter1:buildfromsource [2018/01/03 12:30] (current)
claudio [Building the firmware]
Line 136: Line 136:
  
 The xxxxxxxxxxxxxx should point to suitable headers. In particular on a 64-bit system the system headers might be incompatible and cause errors. The first attempt should be to keep the defaults, and if any errors appear, it needs to be changed to /​usr/​include/​newlib (or wherever there'​s a suitable 32-bit library). While newRPL will not link to or use the library in any way, some standard headers are expected to provide definitions. The xxxxxxxxxxxxxx should point to suitable headers. In particular on a 64-bit system the system headers might be incompatible and cause errors. The first attempt should be to keep the defaults, and if any errors appear, it needs to be changed to /​usr/​include/​newlib (or wherever there'​s a suitable 32-bit library). While newRPL will not link to or use the library in any way, some standard headers are expected to provide definitions.
 +Another possible alternative for 64-bit systems is to install the package libc6-dev-i386,​ which in most cases should allow to keep the default directories.
 For Ubuntu it works with the defaults, for other systems change that to /​usr/​include/​newlib,​ so the line reads: For Ubuntu it works with the defaults, for other systems change that to /​usr/​include/​newlib,​ so the line reads:
  
 ''​INCLUDEPATH += firmware/​include newrpl /​usr/​include/​newlib''​ ''​INCLUDEPATH += firmware/​include newrpl /​usr/​include/​newlib''​
  
-Save and close the file. +Save and close the file. 
 + 
 Now from the top menu, '​Build',​ 'Run QMake',​ then '​Rebuild All'. Now from the top menu, '​Build',​ 'Run QMake',​ then '​Rebuild All'.
 From the bottom of the screen, check the '​Compile Output'​ pane to see if everything went well. There might be some warnings, but there should be no hard errors. There could be many warnings, depending on your version of gcc and your system these warnings change all the time but they are harmless. From the bottom of the screen, check the '​Compile Output'​ pane to see if everything went well. There might be some warnings, but there should be no hard errors. There could be many warnings, depending on your version of gcc and your system these warnings change all the time but they are harmless.
  • manual/chapter1/buildfromsource.txt
  • Last modified: 2018/01/03 12:30
  • by claudio