libuv build shouldn't silently fail if dev dependencies are missing

[Gadnief]

I know that raspbian is not official supported on iot-edge but i wanted to build it on my pi3. It always stopps at the same error:

/home/pi/Downloads/iot-edge/proxy/outprocess/src/module_loaders/outprocess_loader.c:8:16: fatal error: uv.h: Datei oder Verzeichnis nicht gefunden
#include <uv.h>

compilation terminated.
core/CMakeFiles/gateway_static.dir/build.make:230: recipe for target 'core/CMakeFiles/gateway_static.dir//proxy/outprocess/src/module_loaders/outprocess_loader.c.o' failed
make[2]: *** [core/CMakeFiles/gateway_static.dir//proxy/outprocess/src/module_loaders/outprocess_loader.c.o] Error 1
CMakeFiles/Makefile2:987: recipe for target 'core/CMakeFiles/gateway_static.dir/all' failed
make[1]: *** [core/CMakeFiles/gateway_static.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

As far as i can see it can't find the uv.h file. My cmake is at the newest version.

[damonbarry]

When you build our out-of-process module support (outprocess_loader.c is part of that feature) it builds libuv first, so the uv.h header file ought to be there. However, if you haven't installed the necessary dev dependencies for libuv, that part of the build will silently fail. So that's likely what happened here: you built, libuv failed to build but our script kept going, and then you hit a compiler error farther down the line.

The silent failure is a bug that we should investigate and fix, so I'll change the name of this issue and we'll track it as a bug.

But there are two options to get this working for you:

1. Install the needed dev dependencies (more info here):

sudo apt-get install -y libtool autoconf

2. Disable the out-of-process modules feature:

tools/build.sh --disable-native-remote-modules --disable-nodejs-remote-modules [more options...]

[damonbarry]

PR #568 will fix this