googlesamples / assistant-sdk-cpp

Example of Google Assistant gRPC in C++
Apache License 2.0
96 stars 45 forks source link

make run_assistant failed. #38

Open sakthisg opened 6 years ago

sakthisg commented 6 years ago

Just followed the readme and try to build the run_assistant..getting an error? Please help to check what is the issue? ~/Linux-Google-Home/assistant-sdk-cpp$ make run_assistant find: /googleapis/gens/google/api': No such file or directory find:/googleapis/gens/google/rpc': No such file or directory find: `/googleapis/gens/google/type': No such file or directory protoc -I=./googleapis/google/assistant/embedded/v1alpha2 --proto_path=.:./googleapis \ --cpp_out=/googleapis/gens/google/assistant/embedded/v1alpha2 \ --grpc_out=/googleapis/gens/google/assistant/embedded/v1alpha2 \ --plugin=protoc-gen-grpc=/usr/local/bin/grpc_cpp_plugin \ ./googleapis/google/assistant/embedded/v1alpha2/embedded_assistant.proto /googleapis/gens/google/assistant/embedded/v1alpha2/: No such file or directory make: *** [/googleapis/gens/google/assistant/embedded/v1alpha2/embedded_assistant.pb.cc] Error 1 __git_ps1: command not found

Fleker commented 6 years ago

It looks like you didn't clone or compile the protos first? Can you confirm that you have the googleapis directory?

sakthisg commented 6 years ago

Yes I have checked..it is there

On Tue, 7 Aug 2018, 23:21 Nick, notifications@github.com wrote:

It looks like you didn't clone or compile the protos first? Can you confirm that you have the googleapis directory?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/googlesamples/assistant-sdk-cpp/issues/38#issuecomment-411144464, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad-rXxp5IUtTRTF4AxIdiM1a6mDtJdsxks5uOdO1gaJpZM4Vxz5r .

Fleker commented 6 years ago

I've scheduled a CI build to see if I can reproduce.

Have you synced with the most recent changes to the Makefile? If so, maybe going back a few commits may yield better results. I know the most recent PR made some changes to the Makefile.

git checkout f88a48e2ba952c244037918fb0e3a0297fb2bab0 should take you back to a recent commit.

Fleker commented 6 years ago

Is your issue related to #35? Can you delete the googleapis/google/ads directory and see if there's an issue?

sakthisg commented 6 years ago

I have deleted the directory before logging an issue. Will check with recent changes after updating codebase... thanks

On Thu, 9 Aug 2018, 06:23 Nick, notifications@github.com wrote:

Is your issue related to #35 https://github.com/googlesamples/assistant-sdk-cpp/issues/35? Can you delete the googleapis/google/ads directory and see if there's an issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/googlesamples/assistant-sdk-cpp/issues/38#issuecomment-411601939, or mute the thread https://github.com/notifications/unsubscribe-auth/Ad-rX633SNm3v_c_dSXCSTfAmDWDyPO6ks5uO4fzgaJpZM4Vxz5r .

sakthisg commented 6 years ago

Thanks Fleker...Now the build error is solved by taking the recent commit. When i try to execute the step 6 and try to click the link to get the code it is giving me Error 500 (Server error): So i am not able to get the CODE..Can you give guidance to overcome this?


Get credentials file. It must be an end-user's credentials.

Go to the Actions Console and register your device model, following these instructions
Move it in this folder and rename it to client_secret.json
run get_credentials.sh in this folder. It will create the file credentials.json.

sakthi@indbrnblx039:~/Linux-Google-Home/assistant-sdk-cpp ((f88a48e...))$sudo ./get_credentials.sh Client id: 215236190270-gvsipi4d1t3nkdgd8d7l43j0h4k87drq.apps.googleusercontent.com Client secret: TYdAXtgckAePPqmN2fBOUKGb

Please go to the following link to authorize, and copy back the code here: https://accounts.google.com/o/oauth2/v2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fassistant-sdk-prototype&access_type=offline&include_granted_scopes=true&state=state&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&client_id=215236190270-gvsipi4d1t3nkdgd8d7l43j0h4k87drq.apps.googleusercontent.com

Fleker commented 6 years ago

You may need to first setup an OAuth consent screen

image