Mike

Hi @stokersoft, see #1887

Sming 4.0 will require a little re-orientation as there are a lot of changes, not least of which is the documentation at https://sming.readthedocs.io/en/latest/. I heartily recommend you find some quiet...

And please feel free to make any suggestions for improvements. You can also find us at https://gitter.im/SmingHub/Sming

@jensahylda You can follow the instructions on that page as-is, there is no need to change the version number since we only need the toolchain. I agree the instructions are...

https://conan.io Looks promising. @aemseemann you mentioned it in the CMake thread, any thoughts?

> I wonder why all the submodules of the top level Sming repositories are submodules Historical! > ... fetch them on demand from an URL/commit HASH given in component.mk I...

Clearly adopting any package manager is going to require customisation, and if it doesn't make our life easier then we don't do it. Something I didn't mention in the opening...

> fetch all submodules and patch them at once Yes, we'll need this to build the docs too.

@slaff Your submodule archive, do you do that manually? Is that something worth integrating into the build system?

Should we be looking at git subtrees instead, or other similar solutions https://codeburst.io/4-git-submodules-alternatives-you-should-know-592095859b0 I haven't used subtrees at all, but the article says "As opposed to submodules, subtrees’ sources files...