You are correct, iot-devkit-poky.zip is indeed the source for the image. Edison's documentation is currently not available in Github. Nevertheless, I will make sure to pass your feedback about the documentation and your suggestion about posting it on Github to the appropriate team. I apologize if this caused any issues.
The build process stopped on this error, missing http://git.eclipse.org/gitroot/paho/org.eclipse.paho.mqtt.c.git
Though this repo exists http://git.eclipse.org/c/paho/org.eclipse.paho.mqtt.embedded-c.git/ (last touched 10 months ago)
I've change the url in /poky/meta-intel-..../recipes-connec.../paho-mqtt_3.1.bb but the build process used the old url.
Another user had the same issue in https://communities.intel.com/thread/101849. Could you please check that the modifications you did are the same as those made in that thread.
Let me know if this helps you, I'd be glad to help if otherwise.
I went instead with the docker version published by another user on this forum.
From that I managed to get a working build.
I'm puzzled by the suggested change.
It was suggested a month before the last release, how come that change was not in the final release?
Still I managed to build it using the other users Dockerfile.
One explanation is that the reviewed pdf is out of date. The sequence of commands suggested in the pdf differs from what is found in the new source release.
Thus the commands in the pdf trigger a build of paho-mqtt which is otherwise not build?
Perhaps paho-mqtt is no longer needed? If so the reference to it could be completely removed from the source release.
I just want to add that I admire the simplicity of the latest source release in that the build commands included in the zip is all that is needed.
The problem that I have had comes from that I've relied on older documents(although the latest ones available).
This is the reason for the title of this thread, hosting the docs in a single location, easily updated and fixed by community.
I understand how you feel, please believe me we appreciate your feedback, I will make sure it is hear my the appropriate team. We are constantly working on improving our services and hopefully we can make acommunity that's better day by day.
Anyhow, I'm glad to hear that you were able to solve the issue by using the other user's method. And if you have any other doubts, please don't hesitate to come back to the community, we'll try to help you in any way we can.