-
Notifications
You must be signed in to change notification settings - Fork 820
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
build.sh is missing in go directory for SDK #1039
Comments
I think that's more of a warning than an actual issue - @cyriltovena you did this work, yes? According to the readme:
|
Would it be better to have a build.sh that is a no-op to get rid of the error then? I ran into the same thing when I was first poking at the SDKs and found it confusing. |
I don't have strong opinions here 🤷♂️ - @cyriltovena you wrote it? WDYT? |
I don't think you should run If you want to build all of them you can use |
Here is the current output:
I think that the confusion is that a bunch of stuff is printed that looks like an error, but what is happening is that make is printing out a long line of shell that is saying "if the file exists, execute it, and if not print that there is nothing to do". If we suppress the shell command itself, then the output looks a lot nicer:
It prints a message (not an error) but without all of the confusing bits around it. It also looks ok for building the cpp sdk (which is the only one that currently has a build.sh file):
|
When running "make build-sdk" there is an error: "Command build not found - nothing to execute"
The script is looking for build.sh in the default go directory.
According to README build.sh needs to be in the directory.
The text was updated successfully, but these errors were encountered: