Started looking a little more into WSL under Windows 10: https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux
After having successfully compiled and run ODM using WSL, I was wondering how to improve things. Docker's great, but it's not the easiest it could be. Ideally I would like to run something like:
C:\ odm.exe --project-path Users\myuser\drone myproject
And be done with it. No compilation should be required and paths should be expressed using Windows conventions.
WSL gets us half-way there. You can't just make a tarball of ODM files after compilation, because lib dependencies are embedded within the Ubuntu system, so we still need the full Ubuntu system. But you cannot release a full distro on the Windows Store (not at the moment, anyway).
An interesting module/subproject for ODM would be the creation of a odm.exe wrapper that:
./run.sh.Seems doable to me. Just need to find time 馃槃 and/or other volunteers.
Seems you're about a year ahead of me, but I did just get ODM to run successfully on a very low-powered tablet (I'm on vacation) with 6GB of RAM and 4GB of virtual memory.
The above sounds like a great proposition, I will investigate further if I find the time.
Another alternative might be a PowerShell script?
PowerShell could work also, yes.
I don't think it even needs PowerShell, a straight batch file might work.
If I'm tarballing the OpenDroneMap_v0_3_1 folder, which file extensions and subfolders can I safely exclude for the software to work when restored? I'm thinking of source and object files?
This will be massively useful: https://devblogs.microsoft.com/commandline/share-environment-vars-between-wsl-and-windows/
@pierotofy -- I will close for now.
Yep, the idea was good in principle, but MS has back-tracked on WSL 1.0 and their implementation of WSL 2.0 is a half-baked solution IMO. Pity...
That's such a shame.
Most helpful comment
Seems you're about a year ahead of me, but I did just get ODM to run successfully on a very low-powered tablet (I'm on vacation) with 6GB of RAM and 4GB of virtual memory.
The above sounds like a great proposition, I will investigate further if I find the time.
Another alternative might be a PowerShell script?