Conversation
|
This is based on #23, so that one should very likely go in first, and then this one should be re-based and merged. |
|
There is one open question here: EBcLfSA requires an additional tool to be available. It is called "ELF-Enabler". The purposed of the tool is to post-process an ELF-binary and mark it as "High-Integrity Application (HI-Application; "safe executable", colloquially speaking). This tool will, of course, not exist in any other toolchain. How can such a tool be integrated cleanly? The previous method can be seen in this diff (search for |
81275df to
eeb96a3
Compare
|
Depends on #31 |
4dcf46a to
8bbdb6f
Compare
The merge-base changed after approval.
dba298a to
31ca72d
Compare
31ca72d to
a066106
Compare
|
On top of this one I have this proposal elektrobit-contrib@955ca88 It adds |
a30082b to
612f5ab
Compare
612f5ab to
df844e7
Compare
|
c0c6681 to
a390fcf
Compare
179d390 to
1a713b6
Compare
Added "aarch64-linux-sdk_0.1.0-ebclfsa", a GCC-based toolchain for EB corbos Linux for Safety Applications. This is *not* the final toolchain, since that will require a clang-based compiler and a special libc. However, it can be used to demonstrate functionality. # Conflicts: # examples/MODULE.bazel # extensions/gcc.bzl
1a713b6 to
91f56fa
Compare
nradakovic
left a comment
There was a problem hiding this comment.
LD_LIBRARY_PATH in every package file can be avoided, but we will create follow up on this.
Added "aarch64-linux-gcc-ebclfsa-0.1.0", a GCC-based toolchain for EB corbos Linux for Safety Applications. This is not the final toolchain, since that will require a clang-based compiler and a special libc. Hence, this has a pre-1.0.0 version.