320
edits
Howto:Build and run FlightGear on Raspberry Pi 4: Difference between revisions
Jump to navigation
Jump to search
Howto:Build and run FlightGear on Raspberry Pi 4 (view source)
Revision as of 22:58, 9 June 2020
, 9 June 2020→Raspberry Pi OS 64-bit
| Line 640: | Line 640: | ||
The fix is to edit this file; <code>/flightgear/dnc-managed/flightgear/3rdparty/sqlite3/CMakeLists.txt</code>. Within CMakeLists.txt, change <code>fpic</code> to <code>fPIC</code> | The fix is to edit this file; <code>/flightgear/dnc-managed/flightgear/3rdparty/sqlite3/CMakeLists.txt</code>. Within CMakeLists.txt, change <code>fpic</code> to <code>fPIC</code> | ||
Scott wrote: | |||
<blockquote> | |||
The main difference between -fpic and -fPIC is that little-pic generates | |||
faster code, but severely limits you to a small address space (e.g. 64KB | |||
data buffer). big-PIC will leverage a much larger address space (e.g. | |||
2GB) and therefore requires more address bytes to reach the full address | |||
range. More address bytes equates to a small performance hit. | |||
I don't program the ARM enough to know what the hard limit is when using | |||
-fpic, but whatever the limit is, the compiler is telling you that this | |||
limit has been exceeded. | |||
I always use -fPIC as it is rarely worth the fuss to try -fpic first and | |||
then switch to -fPIC when that fails. | |||
Scott | |||
</blockquote> | |||
===Raspbian=== | ===Raspbian=== | ||