Open brlodi opened 4 years ago
Thanks for the feedback. However, this is sort of an expected behavior. The different make
targets allow to delete the VM, the image, the download, ... and recreate the different files as well. Changing it should be possible, but would need some testing. Leaving this issue open...
I haven't tested it, but it looks like this commit to someone's fork is intended to fix this issue? If it does, perhaps it could be merged upstream to fix it?
Also is there a safe way to move all the files into that directory after install, or would doing so break the VM? Thanks!
Didn’t know this fork. Interesting changes...
To Reproduce Steps to reproduce the behavior:
make all
as described in README.md and follow install process.macOS-VM.efi.vdi
andmacOS-VM.vdi
are located directly in~/VirtualBox VMs
instead of~/VirtualBox VMs/macOS-VM
as is typical for VirtualBox VMs.Expected behavior After install,
macOS-VM.efi.vdi
andmacOS-VM.vdi
should be located in~/VirtualBox VMs/macOS-VM
instead of parallel to it.Additional context