Join GitHub today
why does the usage of graphene in DEBUG mode needs driver? #924
I want to develop app based on graphene in localhost without SGX support. When using the original SGX SDK, it's would be fine without SGX driver installed.
So is it possible to remove the dependencies on SGX drivers to ease local development?
I run on my SGX-enabled machine with SGX SDK 2.5 and SGX Driver 2.5, still got
In file included from sgx_framework.c:6:0: sgx-driver/graphene-sgx.h:8:26: fatal error: isgx_version.h: No such file or directory compilation terminated. Makefile:58: recipe for target 'sgx_framework.o' failed make: *** [sgx_framework.o] Error 1 make: Leaving directory '/home/block01/Workspaces/lixiangmin01/graphene/Pal/src/host/Linux-SGX' Makefile:95: recipe for target 'host_lib_recurse' failed make: *** [host_lib_recurse] Error 2 make: Leaving directory '/home/block01/Workspaces/lixiangmin01/graphene/Pal/src' Makefile:7: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/home/block01/Workspaces/lixiangmin01/graphene/Pal' Makefile:8: recipe for target 'all' failed make: *** [all] Error 2
Any help would be greatly appreciated~
Replies for your two questions:
In general, it is not obvious why Graphene-SGX in simulation mode would be useful. If you are deploying your applications on top of Graphene, you can always try your application in non-SGX (normal Linux PAL) mode. If you need to change/use something specific to SGX, then it only makes sense to develop on an SGX-enabled machine.