Skip to content

Compilation Errors (Linux) #2386

Closed
Closed
@Trey2k

Description

@Trey2k

How are you using the lua-language-server?

Other

Which OS are you using?

Linux

What is the issue affecting?

Other

Expected Behaviour

Expected it to be able to compile.

Actual Behaviour

Errors out with

[62/90] Compile C++ build/obj/code_format/Utf8.obj
FAILED: build/obj/code_format/Utf8.obj
gcc -MMD -MT build/obj/code_format/Utf8.obj -MF build/obj/code_format/Utf8.obj.d -std=c++17 -O2 -Wall -fvisibility=hidden -I3rd/EmmyLuaCodeStyle/Util/include -I3rd/EmmyLuaCodeStyle/CodeFormatCore/include -I3rd/EmmyLuaCodeStyle/LuaParser/include -I3rd/bee.lua/3rd/lua -I3rd/EmmyLuaCodeStyle/3rd/wildcards/include -DNDEBUG -Wall -Werror -o build/obj/code_format/Utf8.obj -c 3rd/EmmyLuaCodeStyle/Util/src/Utf8.cpp
In file included from 3rd/EmmyLuaCodeStyle/Util/src/Utf8.cpp:1:
3rd/EmmyLuaCodeStyle/Util/include/Util/Utf8.h:18:1: error: ‘uint32_t’ does not name a type
   18 | uint32_t Utf8ToUnicode(const char *source, std::size_t maxNum, std::size_t &byteNum);
      | ^~~~~~~~
3rd/EmmyLuaCodeStyle/Util/include/Util/Utf8.h:4:1: note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
    3 | #include <string>
  +++ |+#include <cstdint>
    4 | #include <string_view>
3rd/EmmyLuaCodeStyle/Util/src/Utf8.cpp:120:1: error: ‘uint32_t’ does not name a type
  120 | uint32_t utf8::Utf8ToUnicode(const char *source, std::size_t maxNum, std::size_t &byteNum) {
      | ^~~~~~~~
3rd/EmmyLuaCodeStyle/Util/src/Utf8.cpp:2:1: note: ‘uint32_t’ is defined in header ‘<cstdint>’; did you forget to ‘#include <cstdint>’?
    1 | #include "Util/Utf8.h"
  +++ |+#include <cstdint>
    2 |

Seems like the error suggests, the cstdint include is missing. This started happening after 13aebe5

Reproduction steps

  1. Clone ed2df50 and run ./make.sh on a linux system.

Additional Notes

I am currently in the process of integrating the Lua Language Server with the Godot editor. For in editor Lua support. As I mainly run on Linux this means if I wanted to get sockets working for the JSONRPC I would need the ability to run it under Linux.

The reason I am currently trying to build it is I have been following the progress somewhat of #2382 and wanted to test recent changes.

So far I have continued work on my side working directly with STDIN and STDOUT, but overall I would prefer to use sockets to communicate.

I appreciate the work that happens with this project and look forward to future Linux support!

Log File

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    compileRelated to compiling the server from sourceos/LinuxThe server is running on Linux

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions