Describe the bug
Right now when you build an application it will use the name convention from the parent directory of that application, instead of using the name from kraft.yaml. This bug also caused this problem #80 .
To Reproduce
Steps to reproduce the behavior:
1.git@github.com:unikraft/app-helloworld.git
cd app-helloworold
kraft configure -p kvm -m x86_64
kraft build
Expected behavior
After building an application with the name example from kraft.yaml, the unikernel executable should have the name example_kvm-x86-64 even though the parent directory where this application has a different name.
Screenshots
Desktop (please complete the following information):
Describe the bug Right now when you build an application it will use the name convention from the parent directory of that application, instead of using the name from
kraft.yaml
. This bug also caused this problem #80 .To Reproduce Steps to reproduce the behavior: 1.git@github.com:unikraft/app-helloworld.git
Expected behavior After building an application with the name
example
fromkraft.yaml
, the unikernel executable should have the nameexample_kvm-x86-64
even though the parent directory where this application has a different name.Screenshots
Desktop (please complete the following information):
Additional context