- 
                Notifications
    You must be signed in to change notification settings 
- Fork 188
Draft PR covering Canonical packaging dev changes #466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
21435f0
              81dd7c4
              2dfa977
              de40d83
              1cf741c
              File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | 
|---|---|---|
|  | @@ -32,8 +32,8 @@ | |
| include ../../buildenv.mk | ||
|  | ||
| INCLUDE += -I. -I../inc | ||
| INCLUDE += -I$(SGX_SDK)/include \ | ||
| -I$(COMMON_DIR)/inc/internal \ | ||
| INCLUDE += -I$(SGX_TRUSTED_INCLUDE_PATH) \ | ||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we have access to specific location (path) and content of the specific SDK include path? Is it simply a regular SGX SDK's include directory (built from Open Source or installed from Intel provided bin) but located outside of default installation location? E.g., SDK sub-dirs are located in Ubuntu-specific areas depending on the nature of the files? | ||
| -I$(COMMON_DIR)/inc/internal \ | ||
| -I$(COMMON_DIR)/inc/internal/linux | ||
|  | ||
| INCLUDE += -I$(ROOT_DIR)/ae/common \ | ||
|  | @@ -43,7 +43,7 @@ INCLUDE += -I$(ROOT_DIR)/ae/common \ | |
| CXXFLAGS += -fPIC -Werror -g | ||
|  | ||
| CFLAGS += -fPIC -Werror -g | ||
| Link_Flags := $(SGX_COMMON_CFLAGS) -L$(ROOT_DIR)/build/linux -L$(SGX_SDK)/lib64 -lsgx_urts -lpthread -ldl | ||
| Link_Flags := $(SGX_COMMON_CFLAGS) -L$(ROOT_DIR)/build/linux -L$(SGX_LIBRARY_PATH) -lsgx_urts -lpthread -ldl | ||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we have access to specific location (path) and content of the specific SDK library path? Is it simply a regular SGX SDK's library directory (built from Open Source or installed from Intel provided bin) but located outside of default installation location? E.g., SDK sub-dirs are located in Ubuntu-specific areas depending on the nature of the files? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could you elaborate a little bit more on your question ? The idea of this diff, I believe, is to use the right variable  | ||
|  | ||
| vpath %.cpp .. | ||
| vpath %.c $(COMMON_DIR)/src | ||
|  | ||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|  | @@ -33,15 +33,14 @@ | |||||
| DCAP_TOPDIR = ../../.. | ||||||
| include $(DCAP_TOPDIR)/QuoteGeneration/buildenv.mk | ||||||
|  | ||||||
| PREBUILD_OPENSSL_PATH := $(DCAP_TOPDIR)/prebuilt/openssl | ||||||
| FLAGS := -fpie -g -I./ \ | ||||||
| -I$(SGX_SDK)/include \ | ||||||
| -I$(DCAP_TOPDIR)/external/jwt-cpp/include \ | ||||||
| -I../../QVL/Src/ThirdParty/rapidjson/include \ | ||||||
| -I$(DCAP_TOPDIR)/QuoteGeneration/common/inc/internal/ \ | ||||||
| -I$(DCAP_TOPDIR)/QuoteGeneration/common/inc/internal/linux/ \ | ||||||
| -I$(PREBUILD_OPENSSL_PATH)/inc \ | ||||||
| -I../common | ||||||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 
        Suggested change
       
 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks @bgotowal for this fix, Lgtm | ||||||
| $(CRYPTO_INC) | ||||||
|  | ||||||
| ifdef DEBUG | ||||||
| FLAGS += -DSE_DEBUG_LEVEL=SE_TRACE_DEBUG | ||||||
|  | @@ -56,7 +55,7 @@ Cpp_Common_Obj_Files := file_util.o format_util.o | |||||
| C_Obj_Files := se_trace.o | ||||||
|  | ||||||
| Obj_Files := $(Cpp_Files:.cpp=.o) $(C_Obj_Files) $(Cpp_Common_Obj_Files) | ||||||
| LDFLAGS += -L$(PREBUILD_OPENSSL_PATH)/lib/linux64 -lcrypto -lpthread -ldl | ||||||
| LDFLAGS += $(CRYPTO_LIB) -lpthread -ldl | ||||||
|  | ||||||
|  | ||||||
| TARGET_NAME := tee_appraisal_tool | ||||||
|  | ||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding warning about potential pkg-config issues (and/or not installed) to be considered plus fallback mechanism:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in case CRYPTO_LIB and CRYPTO_INC cannot be retrieved with pkg-config, we can stop and output an error message