Move all enclave apps to a single workspace#3892
Move all enclave apps to a single workspace#3892conradgrobler merged 4 commits intoproject-oak:mainfrom
Conversation
f80fc10 to
e43555b
Compare
|
Can you remind me what stops us from merging even those in the main workspace? If it's just that the cargo config files need to be close to the individual crates, couldn't that be solved by just creating a subfolder (may be |
|
That actually works in the same workspace, as long as it is built from within the project directory and the It turns out we can even move the restricted kernel and stage 0 to the same workspace, as long as we specify a different linker script path (it seems that |
f60aa33 to
53d3be8
Compare
|
I want to make sure we can keep running |
|
It seems stage0 has linking issues when it is in the same workspace, so I will leave it out for now, but I will move everything else into a single workspace. |
|
It's fine if we need to do something more in order to actually build those binaries correctly, but the default commands must still at least do something sensible. |
Ah, no it doesn't. I will revert the last commit. |
53d3be8 to
e2f701d
Compare
One option here is to specify the |
|
Artifact name: quirk_echo_enclave_app Provenance digest: |
|
Artifact name: oak_echo_raw_enclave_app Provenance digest: |
|
Artifact name: oak_echo_enclave_app Provenance digest: |
|
Artifact name: oak_restricted_kernel_bin Provenance digest: |
|
Artifact name: stage0 Provenance digest: |
|
Artifact name: oak_restricted_kernel_simple_io_bin Provenance digest: |
|
Artifact name: oak_functions_enclave_app Provenance digest: |
|
Artifact name: oak_tensorflow_enclave_app Provenance digest: |
Fixes #3889