I cant install swag

Your swag version
last
Your go version
1.13.6 windows/amd64
Same here, for a workaround I use the binary of this release https://github.com/swaggo/swag/releases/tag/v1.6.4
Same here, for a workaround I use the binary of this release https://github.com/swaggo/swag/releases/tag/v1.6.4
thanks, how can i install binary file?
Same here, for a workaround I use the binary of this release https://github.com/swaggo/swag/releases/tag/v1.6.4
thanks, how can i install binary file?
A better solution for your case is just to use this command:
go get -u github.com/swaggo/swag/cmd/[email protected]
In my case I was using a dockerfile and I just needed the binary, so I used wget to download it and I used it.
v1.6.4 or v1.6.5 ?
v1.6.4 or v1.6.5 ?
Last one, v1.6.5, also it is the same error as this old issue https://github.com/swaggo/swag/issues/556, but the fix got reverted recently.
@easonlin404
1.6.5
@bkocadere I think it caused by GO111MODULE=auto, can you execute:
export GO111MODULE=on
and try again
go get -u github.com/swaggo/swag/cmd/swag
@bkocadere I think it caused by
GO111MODULE=auto, can you execute:export GO111MODULE=onand try again
go get -u github.com/swaggo/swag/cmd/swag
thanks, how can use 'export' in cmd screen ?
sorry, I didn't note that you use windows environment, please refer https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt/79614 to set environment variables like:
SET GO111MODULE=on
sorry, I didn't note that you use windows environment, please refer https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt/79614 to set environment variables like:
SET GO111MODULE=on
thanks , working
You shouldn't close this issue, the bug is still here.
@bkocadere I think it caused by
GO111MODULE=auto, can you execute:export GO111MODULE=onand try again
go get -u github.com/swaggo/swag/cmd/swag
thanks bro it's working
Please use the latest version against master to try again, the issue shoud be fixed by #618.
Most helpful comment
You shouldn't close this issue, the bug is still here.