Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
R
RTEMS-build-workflows
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Thanassis Tsiodras
RTEMS-build-workflows
Commits
2ee62670
Commit
2ee62670
authored
Mar 17, 2016
by
Thanassis Tsiodras
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Document the challenges and the solutions chosen
parent
60e01207
Pipeline
#39
skipped
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
22 additions
and
0 deletions
+22
-0
doc/README.md
doc/README.md
+22
-0
No files found.
doc/README.md
0 → 100644
View file @
2ee62670
Building RTEMS applications using EDISOFT/OAR
=============================================
This document explains in detaill the technical challenges that drove
the creation of the sample Makefiles in this repository.
Note that you don't need to know these details to create your applications;
but if you want to know why the Makefiles are structured the way they are,
and what the options used mean, this document sheds light into the issues
that forced the specific choices.
## The native FPU challenges - and how to cope
TBD
## Differences between your API invocations across EDISOFT / OAR
TBD
## Link suggestions
TBD
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment