-
Notifications
You must be signed in to change notification settings - Fork 25
Trying to resolve issue 41 on custom device and still getting failures - need assistance #47
Comments
We have been collaborating with Amazon to integrate alexa smart screen assistant integrated on our latest CommScope products. We have demonstrated it for about 6 months to several customers. All of our demonstration builds are now broken. Also, we work closely with Broadcom and their BVoice implementation uses alexa multimode version 2.01 and their implementation is also broken. |
Closed issue by mistake - sorry. Reopening. |
We have integrated/demo's alexa smart screen assistant 2.0.1 and had no issues with the build. We are upgrading to alexa smart screen assistant 2.2.1 to go along with alexa avs 1.20.1. Our goals are the following:
|
CMakeLists.txt |
It looks to me like I am getting the same exact error even if I copy the package-lock.json file from issue 41 package-lock.json.zip. after the install and before the build. Here is the resultant directory info. |
We are using npm -version 3.5.2 on our build server. Could this be an issue since it is so old? |
Hi cdelsordo, For this release there is no need to copy over the package-lock as we have included in already: Please make sure your node_module (inside module/GUI/js folder) has been deleted before trying to rerun make. It could be possible the npm version is out of date, as i'm currently on:
and
Quick way to test this, would be by going to ../moodules/GUI/js and run Let me know what the results you are getting from this, or are you able to build with no errors? (you can ignore the yellow warnings) |
We have not yet upgraded to 2.3.0. I can do that today and try it. Also I will move to apl-core 1.4 as smart screen 2.2.1 was not compatible with apl-core 1.4. |
I upgraded to apl-core 1.4 and alexa smart screen assistant 2.3.0 and remove the package-config.json workaround and still got an error
/usr/bin/env: ‘node’: No such file or directory npm ERR! Linux 4.4.0-176-generic npm ERR! Please include the following file with any support request: npm ERR! Linux 4.4.0-176-generic npm ERR! Please include the following file with any support request: So the error does indicate that I should try the latest npm and nodejs as a first step. I next try and upgrade. |
Looks like node binary is not on your $PATH. If you are having trouble with Symlink you can always add node to your path I believe uninstalling both node and npm and reinstalling the latest should fix everything nevertheless. Hope this helps |
Upgraded the npm version on my build machine and that issue is now resolved. Do I need to open another ticket to address the following new issue? I am now seeing that all the unit tests are failing. I must have something not configure correctly. Any hints? The build error is below: | [50/52] : && /export/cdelsordo/smd7852/build-smd7852/tmp/sysroots/x86_64-linux/usr/bin/arm-rdk-linux-gnueabi/arm-rdk-linux-gnueabi-g++ -DRAPIDJSON_PARSE_DEFAULT_FLAGS=36 -DDEBUG -DACSDK_DEBUG_LOG_ENABLED -Wall -Wsign-compare -g -DRAPIDJSON_HAS_STDSTRING -march=armv7ve -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a15 -fno-omit-frame-pointer -fno-optimize-sibling-calls --sysroot=/export/cdelsordo/smd7852/build-smd7852/tmp/sysroots/smd7852 -Os -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/export/cdelsordo/smd7852/build-smd7852/tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/alexa-mm/2.3.0-r0=/usr/src/debug/alexa-mm/2.3.0-r0 -fdebug-prefix-map=/export/cdelsordo/smd7852/build-smd7852/tmp/sysroots/x86_64-linux= -fdebug-prefix-map=/export/cdelsordo/smd7852/build-smd7852/tmp/sysroots/smd7852= -fvisibility-inlines-hidden -march=armv7ve -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a15 -fno-omit-frame-pointer -fno-optimize-sibling-calls --sysroot=/export/cdelsordo/smd7852/build-smd7852/tmp/sysroots/smd7852 -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -L/usr/lib -lssl -lcrypto -lnghttp2 -lz -lffi -lgmodule-2.0 -lpthread -lffvss -lnexus -Wl,--disable-new-dtags -rdynamic modules/Alexa/APLClientLibrary/APLClient/test/CMakeFiles/AplCoreGuiRendererTest.dir/AplCoreGuiRendererTest.cpp.o -o modules/Alexa/APLClientLibrary/APLClient/test/AplCoreGuiRendererTest -Wl,-rpath,/export/cdelsordo/smd7852/build-smd7852/tmp/work/cortexa15t2hf-neon-rdk-linux-gnueabi/alexa-mm/2.3.0-r0/build/modules/Alexa/APLClientLibrary/APLClient/src modules/Alexa/APLClientLibrary/APLClient/src/libAPLClient.so modules/Alexa/ThirdParty/googletest-release-1.8.0/googlemock/libgmock_main.a -Wl,-rpath,/lib -latomic -Wl,-Bstatic -lapl -lyogacore -Wl,-Bdynamic -lpthread && : |
Hi yes please re-open a new ticket only because future Github users can also track this issue if they face a similar situation and it'll be easier if it's on its separate thread. Thanks! |
IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
I am working on a fix to what I believe is due to issue 41 in a yocto based build system and cannot get it to work
What is the expected behavior?
alexa smart screen should build
What behavior are you observing?
build is still failing. Due to the nature of yocto recipe I chose to modify GUI/MakeLists.txt make file to carry out the steps in issue 41
Here is the patch of modules/GUI/CMakeLists,txt copying the issue 41 zip file version of package-lock.json after the npm install results in it not being over written. I also tried the build with and without the removal of the directory ../js/node_modules and I am still getting an error.
Can you help me with this patch to overcome this issue. Do you know when this npm server problem will be resolved?
--- a/modules/GUI/CMakeLists.txt
+++ b/modules/GUI/CMakeLists.txt
@@ -15,7 +15,10 @@
add_custom_target(GUIClient ALL
COMMAND "cp" "${CMAKE_CURRENT_SOURCE_DIR}/config/StartSample.sh" "${AlexaSmartScreenSDK_BINARY_DIR}"
+# COMMAND "rm" "-rf" "${CMAKE_CURRENT_SOURCE_DIR}/js/node_modules"
COMMAND "npm" "run" "build" "--"
"--output-path" "${CMAKE_CURRENT_BINARY_DIR}"
"--define" "DISABLE_WEBSOCKET_SSL=${DISABLE_WEBSOCKET_SSL_VALUE}"
Provide the steps to reproduce the issue, if applicable:
We are going through the same steps to build alexa sdks that we have been doing for about a year and now issue 41 has broken all or our product builds that use alexa smart screen assistant. We are seeing previous versions of alexa smart screen (ie 2.0.1) also have similar build errors.
Tell us about your environment:
RDK Yocto build environment.
What version of the AVS Device SDK are you using?
Tell us what hardware you're using:
Tell us about your OS (Type & version):
Have you tried the same use case with AVS Device SDK SampleApp?
log.do_compile.txt
The text was updated successfully, but these errors were encountered: