Closed stsdc closed 2 years ago
This is a message from the language server though (it just appears as a message from the extension).
Conf.vala
located? Is this a generated file? If so, where is it generated?@stsdc sorry for late reply. What version of VLS do you have? On master I don't seem to have this problem.
Probably something changed in VS Code, because the extension was working like a month or so ago.
I think this has to do with the file you added, Conf.vala
, which ultimately depends on multiple custom targets.
I'm using 0.48.3+r1+pkg1~daily~ubuntu6.1
on elementary.
Can you produce a trace of VLS up to this error?
You need to enable debugging output in the Vala extension.
(vala-language-server:121075): vls-WARNING **: 13:20:53.014: mesonproject.vala:113: for target Conf.vala.in@cus, source #0, could not substitute special arg `@INPUT0@' ... (vala-language-server:121075): vls-DEBUG: 13:20:53.080: project.vala:192: target Conf.vala.in.in@cus will be removed (vala-language-server:121075): vls-DEBUG: 13:20:53.080: project.vala:192: target Conf.vala.in@cus will be removed
This is where things go wrong. I'll try this out on eOS myself and see if I need more info from you.
VLS works again after I did this: https://github.com/stsdc/monitor/commit/93e7a8c8ac2b3004826438bee464ad5f3219ec7a.
I previously mindlessly copypasted some code to generate version string, but didn't really tried to used it until today. I did a refactor today and removed a lot of strange things.
Well that's one way to solve the problem, but VLS 0.48.4 handles the old configuration. Therefore my advice is either to stick with your changes or upgrade to VLS 0.48.4 when you can.
Thanks @Prince781!
Probably something changed in VS Code, because the extension was working like a month or so ago.