Skip to content
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

CompileDaemon did not install with vendor directory #90

Open
DavesPlanet opened this issue Aug 17, 2023 · 1 comment
Open

CompileDaemon did not install with vendor directory #90

DavesPlanet opened this issue Aug 17, 2023 · 1 comment

Comments

@DavesPlanet
Copy link

ran the following in visual studio console in Windows 10
go version go1.20.1 windows/amd64

first I did a go get:

go get github.com/githubnemo/CompileDaemon

then go install

go install github.com/githubnemo/CompileDaemon

received error

go: inconsistent vendoring in C:\projects\gogo:
github.com/fatih/[email protected]: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/fsnotify/[email protected]: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/githubnemo/[email protected]: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/mattn/[email protected]: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
github.com/radovskyb/[email protected]: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
To ignore the vendor directory, use -mod=readonly or -mod=mod.
To sync the vendor directory, run:
go mod vendor

did what the error said:

go mod vendor

tried again to install, got error

go install github.com/githubnemo/CompileDaemon
go: finding module for package github.com/githubnemo/CompileDaemon
cannot query module due to -mod=vendor
(Go version in go.mod is at least 1.14 and vendor directory exists.)

tried several options for a while, eventually renamed vendor to vendorX, after that the install worked, renamed vendorX back to vendor, the daemon worked.

Thanks for an awesome product, I'm glad I got it to run.

@DavesPlanet
Copy link
Author

I wonder if some of the instructions in the first error about ignoring the vendor directlry could have gotten me through the second error. Maybe just needs a bit more instruction in the second error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant