mirror of https://github.com/rusefi/rusefi.git
41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
|
|
[Doxygen](https://rusefi.com/docs/html/) <<< landing page has best implementation introduction.
|
|
|
|
[Q&A on source code](https://rusefi.com/forum/viewtopic.php?f=5&t=10)
|
|
|
|
See also [../unit_tests](../unit_tests)
|
|
|
|
This directory contains the source code for the RusEFI firmware.
|
|
|
|
The ideal is that typical end users should be able to use pre-built
|
|
firmware. They should not need to modify or even rebuild from the
|
|
source code for basic use, but building from the source code provides
|
|
the opportunity for optimization, supporting unexpected engine
|
|
configurations, and specialized enhancements.
|
|
|
|
|
|
TL;DR
|
|
|
|
``make PROJECT_BOARD=microrusefi PROJECT_CPU=ARCH_STM32F4``
|
|
|
|
# Environment
|
|
|
|
Rebuilding from source code requires this firmware, a modern C/C++
|
|
compiler for embedded ARM systems, and a platform that supports 'make'
|
|
based builds.
|
|
|
|
See setup_linux_environment.sh
|
|
|
|
While many compilers have the potential to work, we suggest using the
|
|
official ARM version of GCC available at launchpad.net.
|
|
|
|
Linux and MacOS systems should have the software development tools,
|
|
primarily 'make', pre-installed or readily installed. MS-Windows
|
|
requires selecting and installing a Unix-compatible system environment.
|
|
|
|
Note that the developers are volunteers, with varied motivations.
|
|
These motivations often include using leading-edge language and build
|
|
system concepts, requiring recent versions of tools. Should you
|
|
encounter build problems, review the latest version of this document.
|
|
|