My expectation & question is:
[
Is there a doc/procedure explain how to build a library after modified ?
e.g. I want to have the version: “7.3” of https://github.com/mongoose-os-libs/mongoose
and add some debug print
]
If you want to modify one of the mongoose-os-libs you should build locally.
If you want to build remotely you will most likely end up getting the unmodified library, what I’ve been doing so far (just what I fancy and works for me) is to place a copy on the deps directory and in mos.yml use - name: libname (instead of - origin: https://github.com/mongoose-os-libs/libname). Before each build, erase the deps and build directories and copy your modified libname contents to deps/libname, which is trivial from the command line.
This works also for developing your own lib. Most developers seem to use Docker and build locally.
Yes, that’s the way I do it all the time. And I have lots of common code and libraries which are placed in directories out of the application’s source tree.
This layout works for remote builds too, provided the size of the upload is les than ~5MB, I think. There is no need to play with the deps directory and local builds anymore.
LE. Forgot to mention the posibilty to create a private build server. It works for me on Debian buster.
I read somewhere a response to a similar question. IIRC and my understanding was correct, Mongoose comes bundled with mOS and you can not (easily ?) change to a different release; furthermore, the API in version 7 is different and mOS may not be ported to that API, at least in the near future.
Error: /src/cli/manifest_parser/manifest_parser.go:425: neither sources nor prebuilt binary exists for the lib “dash” (or, if a library doesn’t have any code by design, its mos.yml shouldn’t contain “sources”). Fetch error was: [unable to fetch prebuilt binary for “dash”]