#fumo-compiler
1071 messages ยท Page 2 of 2 (latest)
and some diagnostics for CMAKE_CXX_COMPILER_CLANG_SCAN_DEPS-NOTFOUND
thats because you dont have clang installed on your system
i could warn the users about that
once again, you can use gcc if you prefer. i use clang because gcc outputs flags that break clangd lsp
i can add some warnings for users though, sure
ill update the script to warn users
that is weird, I'm compiling my lang with clang ๐

-- Check for working CXX compiler: /usr/bin/clang++ - skipped
weird, the output you sent seems to be complaining about not finding clang though huh
ntu clang version 18.1.3 (1ubuntu1)
Target: x86_64-pc-linux-gnu
try adding
set(CMAKE_CXX_SCAN_FOR_MODULES OFF)
to the CMakeLists.txt
add it at the start, it might fix it
its trying to use clang-scan-deps because i didnt disable modules, and you dont have clang tools on your system
still says skipped but got to compilation errors
/usr/bin/clang++ -DCPPTRACE_DEMANGLE_WITH_CXXABI -DCPPTRACE_GET_SYMBOLS_WITH_LIBDWARF -DCPPTRACE_HAS_CXX_EXCEPTION_TYPE -DCPPTRACE_HAS_DL_FIND_OBJECT -DCPPTRACE_STATIC_DEFINE -DCPPTRACE_UNWIND_WITH_UNWIND -DLIBASSERT_STATIC_DEFINE -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/usr/lib/llvm-18/include -I/home/zean/fumo/fumo-compiler/src -I/home/zean/fumo/fumo-compiler/build/_deps/libassert-src/src -isystem /home/zean/fumo/fumo-compiler/build/_deps/libassert-build/include -isystem /home/zean/fumo/fumo-compiler/build/_deps/libassert-src/include -isystem /home/zean/fumo/fumo-compiler/build/_deps/cpptrace-src/include -isystem /home/zean/fumo/fumo-compiler/build/_deps/cpptrace-build/include -O0 -g -fsanitize=address,leak -fno-omit-frame-pointer -Werror -Wall -Wno-unused-variable -g -std=gnu++23 -MD -MT CMakeFiles/fumo.dir/src/codegen/llvm_codegen.cpp.o -MF CMakeFiles/fumo.dir/src/codegen/llvm_codegen.cpp.o.d -o CMakeFiles/fumo.dir/src/codegen/llvm_codegen.cpp.o -c /home/zean/fumo/fumo-compiler/src/codegen/llvm_codegen.cpp
much better ๐
where is the error 
error: no template named 'expected' in namespace 'std'; did you mean
also, its strange you are getting these. i tested the compiler on 6 different machines (unrelated to mine) and it worked fine
does not compile with 23
i might need to add more coverage for people with systems without all the stuff installed
std::expected is only on cpp23
i dont end up actually using it in the code for the current codebase
but you should be compiling fine if you have cpp23
things like this are a bit of a nightmare ๐
i'm slowly writing the "isntall.md" and it is ahrd
delete these lines if you dont want to add c++23 to your system
it might work in cpp20 (which i assume you are using)
i didnt have these version/install issues in the machines i tested it on, so i didnt know youd run into these things
probably needs a -std=c++23
other people here managed to build it
i see a -std=gnu++23
it does
ye weird, it should be the clang one anyway
it might not matter, though
the default version for cpp is c++11
this kinda thing shows up when its using c++11
so it might somehow be using the wrong language version
i have no idea what kinda thing is going on in your machine
but its strange that the cmakelists and the scripts didnt simply work

from the build folder I can run that individual command and it gives the same error
there is something wrong with c++
that's why i still use 11 ๐
well, my compiler expects cpp23 (probably cpp20 works too)
what version of clang do you have?
and that's why it skipped clang++
good, now cmake is in endless loop stuck on clang 18 ๐
for the loop, looks like you can't set the compiler after the project
set(CMAKE_EXPORT_COMPILE_COMMANDS ON)
set(CMAKE_CXX_SCAN_FOR_MODULES OFF)
set(CMAKE_CXX_COMPILER "/usr/bin/clang++-20")
project(fumo LANGUAGES CXX)
@gaunt verge
Note: Make sure to use back-ticks (`) and not quotes (')
Note: Make sure to specify a highlighting language, e.g. `cpp`, after the back-ticks
```cpp
int main() {}
```
int main() {}
how do i make without calling install script each time?
spent until now to troubleshoot, some progress, but definitely won't work
this is probably too cutting edge
damn, definitely didnt expect that to be an issue
i'll check it out sometimes in the future
until then I can look over the code
but I'm seriously considering giving up on LLVM support: one person can't realistically do more than one backend...
though I was hoping for some compilation speed out of LLVM
how's your compilation speed?
i havent tried massive programs but its basically immediate for all my inputs
guys fumo compiler is on hold right now (i was finishing up generics)
because i have to study for exams
and because im focused on submitting patches to gcc

once thats chill ill go back to working on this
Cool cool