While compiling my C library for micropython as a native mpy module, I wondered about distribution.
There are currently several proposed methods:
mip packages installer - should works with mpremote mip alogside with on-board mip. (preffered for me)- writing a oneline command for the REPL using
requests.
- distributing the files as is (via github releases or another delivery method), where the user has to download and install them manually.
If 2 and 3 don't cause me any issues, except for the inconvenience, then I consider the mip option to be the priority because it is a documented way of delivering packages (with mpremote included). But I haven't found a recommended way to do this for packages containing native mpy for different platforms.
Since mip cannot automatically determine the target platform, it is necessary to get out of the situation using non-trivial methods such as distributing package.json separately for each platform using links/indexes/tags/branches/subdirectories whatewer, and the user must specify the platform during download.
While compiling my C library for micropython as a native mpy module, I wondered about distribution.
There are currently several proposed methods:
mippackages installer - should works withmpremote mipalogside with on-boardmip. (preffered for me)requests.If 2 and 3 don't cause me any issues, except for the inconvenience, then I consider the
mipoption to be the priority because it is a documented way of delivering packages (withmpremoteincluded). But I haven't found a recommended way to do this for packages containingnative mpyfor different platforms.Since
mipcannot automatically determine the target platform, it is necessary to get out of the situation using non-trivial methods such as distributingpackage.jsonseparately for each platform usinglinks/indexes/tags/branches/subdirectorieswhatewer, and the user must specify the platform during download.