V: Hardcoded path ~/code/v has been removed. V 0.1.1 can now be installed anywhere.

[medvednikov]

This also fixes Azure CI.

[Chiiruno]

Yay!
Think you could release this as a hotfix release?
Thanks!

[medvednikov]

Of course, I'll release 0.1.1 within 15 minutes.

[medvednikov]

Done, 0.1.1 is live.

[Chiiruno]

Could we update the releases page and the v.c repo to 0.1.1 please?

[ghost]

@medvednikov In my case I've installed it under ~/.vlang, in my .bashrc _export PATH=$PATH:$HOME/.vlang/v/compiler_ however V generates *.c files inside that directory, it could be nice to have those files generated inside ~/.vlang/cache or ~/.vlang/codegen to keep its directory clean.

[nathanKramer]

One thing I noticed is that there are still platform specific third party includes with this hardcoded path, e.g:

https://github.com/vlang/v/blob/353a6edb7c2389d5d10cb0b68ff9504dd54cf392/stbi/stbi.v#L10

When I was setting up the language (very cool by the way!) I had to manually copy some of these thirdparty libraries into my OS' includes directory to get things running, I didn't realise that there was supposed to be an automatic way for this to happen.

Perhaps VROOT can be configured as an env variable, and these includes can be rewritten as #flag darwin -I$VROOT/thirdparty/stb_image

---

edit:

It looks like someone has opened a PR for this:
https://github.com/vlang/v/pull/559

[medvednikov]

This was fixed.