Closed testing-in-chrome closed 4 years ago
A small question, out of curiosity: why do you want to build DLS yourself rather than use the prebuilt brinaries ? Is it on a 32bit system ?
Apparently I don't properly take set the current durectory before doing dub describe
in the preGenerate command, so trying to build outside of the package directory fails.
I'll fix this tonight when getting back to my machine.
This should be fixed with v0.25.18. You'll just have to wait until it's up on code.dlang.org
v0.25.18 is on hold until I figure out why putting out a new release crashes DLS
The push to master automatically closed; but obviously you can always re-open if the issue is not actually fixed. v0.25.19 will be available shortly
Thanks for the fix!
I build it using dub (& usually ldc) to put the binary at a particular location for vim's LanguageClient_Server to be able to locate it.
I'm not sure which language client you are using, but I think you should be able to configure any language client to use a specific path instead. Or, if you really want to access dls from a specific directory, I think it's better to create a symlink from the binary install location to your desired location. DLS will update itself but only install the new version in its predefined position, so you'll have to manually do updates if you compile it yourself
Thanks! How is that predefined position is configured, let's say if I download the linux binary from the "releases" page?
Simply use dub run dls:bootstrap
instead of dub build dls
, this is going to download the latest version and tell you where it is.
Installation and everthing you need to know is in the README 😉
I see my comment before yours even if I posted it after... Is Github drunk ?
I see my comment before yours even if I posted it after... Is Github drunk ?
Seems so! :-D
Run the following:
Get the following error: