Closed buildersbrewery closed 6 years ago
1:11 None error 'stdio.h' file not found 29:12 None error 'iostream' file not found 2:11 None error 'stdlib.h' file not found 24:11 None error 'deque' file not found 4:11 None error 'vector' file not found 1:11 None error 'string.h' file not found 27:11 None error 'lslmini.tab.h' file not found
That looks like the include path is seriously broken, which causes all the other errors. Also, that last file is generated by flex or bison, can't remember which, so it seems that you don't have them either, or that the makefile failed to run them for some reason.
Will you check if attached binary work well? lslint.exe.zip I don't know much about linkages but the recent builds are built with VS 2017 community and that might cause this issue. BTW the build included in my LSL plugin is xp version, which are built with old SDK7.1, not VS 2017.
It doesn't seem to be about the binary/libs, but about the build process (or perhaps the makefile). Somehow it doesn't manage to find include files as basic as iostream
or stdio.h
. I'm not able to reproduce that build environment, so I have no way to debug it.
@buildersbrewery can you reproduce the issue or work well if you build from source?
@Makopo I didn't run the build process as I didn't have too much time yesterday. I'll look into this further and report back.
I'm confused. You can only get these errors while compiling lslint. If you were not doing that, I'd appreciate a more elaborate explanation on what you were trying to achieve and how.
I was looking into how to:
Anyhow, to get back to the topic here:
clangd
. Links in the first post.@Makopo From a usability standpoint all three Windows binaries from v1.0.9
work just fine on my machine.
I wonder if you have a C++ library at all. Usually, compiler packages come with the libraries included, but from the clangd description page, it seems to me that it's just the compiler itself with no libraries.
Also, clangd must somehow find the includes, so I guess there must be some kind of configuration to tell it where the includes and libraries are installed, so even if you have installed them, there may still be a misconfiguration issue.
There's also the issue of needing flex and bison. I wonder if lslint should include the generated lslmini.tab.h in the repository, for the benefit of those who don't have flex or bison installed and don't want to fiddle with lslmini.l or lslmini.y.
@buildersbrewery How did this end up? Should we keep this issue open?
@Makopo I suggest to close this for now. It doesn't seem like something needing any actions from the lslint side. If the OP wants to provide more information on what lslint can do to help with this, it can be reopened.
Since no response from submitter for a while and it seems building environment issue, closing this.
Posting below an output for
lslint v1.0.9
via:Hope this helps with further development.