-
-
Notifications
You must be signed in to change notification settings - Fork 249
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
New language + go generate; does not show up #25
Comments
Odd. I applied your change locally, and both appear in the list of languages for me.
Maybe a path issue? When you run scc are you doing so in the WSL or through CMD? If WSL (which I suspect you are using as you mention I just tried the process both in WSL and CMD using your build without issue, so I am unable to replicate this. If you submit a PR im happy to do the generate for you though. Actually I am faily confident it is just a path issue. Your PR indicates a change to |
I am getting the right path to the updated binary, but it must somehow not get the updated |
Merged and regenerated the constants file. Should be included now if you pull from master. |
scc.exe generates after I am using a direct path to |
No the above should be all that is required. I am totally unable to replicate this. See the below. I first removed a , from the languages.json file and tried to generate which produced the error. I then reverted that change, built as normal and ran scc.exe against the processor directory in the repository. I then removed Go from the list of languages in languages.json ran go generate then go build and then ran the same command to count the processor directory. Unable to recognise Go it returns nothing.
Would you be able to try repeating the above steps for me please. |
I will run this once I'm back at the computer I had this problem with (Tuesday probably). |
Running package processor
const (
) Then go build and run yields:
For whatever reason the updated languages do not appear to be coming from |
Note that I have very limited Go experience, so I might be missing the obvious somewhere... |
That is very odd... if Do you have your GOPATH set correctly? It looks to me as though you have not set it up, and done both a You can verify your gopath on windows by trying Further reading about GOPATH and Go https://boyter.org/posts/how-to-start-go-project-2018/ |
Works great, thanks! |
GOPATH is one of those annoying things. I should look into replacing the current dep with vgo to resolve this. |
I tried to add language support for SAS and Stata, see diff.
I ran
go generate
andgo build
after, but these do not show up in the list when doingscc --languages
nor in the list when running the main version.Running go 1.11 on windows.
Any advice?
The text was updated successfully, but these errors were encountered: