vscode-cmake-tools VS sectorlisp

After that I would recommend installing the MS CMake Tools extensions (https://github.com/microsoft/vscode-cmake-tools/blob/main/do...), this discovers CMakeLists.txt files in the projects and then uses those to setup build- and debugging targets, and in general gives your an IDE-like experience, while still being more transparent than a "fat IDE" like Visual Studio or Xcode.

what do you mean? you need to create a CMakeLists.txt file, the extension can create one for you iirc, take a look at: https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md

#https://medium.com/@onur.dundar1/cmake-tutorial-585dd180109b #https://github.com/microsoft/vscode-cmake-tools/blob/main/docs/README.md cmake_minimum_required(VERSION 3.0.0) project(Zoom VERSION 0.1.0) include(CTest) enable_testing() set(CMAKE_CXX_STANDARD 17) if(${CMAKE_BUILD_TYPE} MATCHES Debug) message("Debug Build") add_definitions(-DDEBUG="Debug Build") elseif(${CMAKE_BUILD_TYPE} MATCHES Release) message("Release Build") add_definitions(-DRELEASE="Release Build") endif() #benXml add_library(benXml STATIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/XmlRessource.cpp) target_sources(benXml PUBLIC ${CMAKE_SOURCE_DIR}/lib/benXml/src/include/tinyxml2.cpp) #benLog FILE(GLOB_RECURSE benLog_all_sources "lib/benLog/*.cpp") add_library(benLog STATIC ${CMAKE_SOURCE_DIR}/lib/benLog/src/Log.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConfig.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogConsoleTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogFileTarget.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/Logger.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogLevel.cpp ${CMAKE_SOURCE_DIR}/lib/benLog/src/LogTarget.cpp ) target_link_libraries(benLog benXml) #Zoom FILE(GLOB_RECURSE all_sources "src/*.cpp") add_executable(Zoom ${CMAKE_SOURCE_DIR}/src/Zoom.cpp) target_sources(Zoom PUBLIC ${all_sources}) target_include_directories(Zoom PUBLIC src lib) target_include_directories(Zoom PUBLIC src) target_link_libraries(Zoom mingw32) target_link_libraries(Zoom SDL2main) target_link_libraries(Zoom SDL2) target_link_libraries(Zoom SDL2_mixer) target_link_libraries(Zoom SDL2_image) target_link_libraries(Zoom SDL2_ttf) target_link_libraries(Zoom box2d) target_link_libraries(Zoom benXml) target_link_libraries(Zoom benLog) set(CPACK_PROJECT_NAME ${PROJECT_NAME}) set(CPACK_PROJECT_VERSION ${PROJECT_VERSION}) include(CPack)

source

It sounds like you don't have a version of make itself installed in your environment. If you're using msys2 as your environment, you might have hit this bug, which at least has a workaround (symbolic link from mingw32-make.exe to make.exe )

Hey, what issues are you seeing with the CMake Tools extension? My team would definitely like to make sure that these issues are tracked here Issues · microsoft/vscode-cmake-tools (github.com). We'll get to them as soon as we can to make sure folks have a great experience with Code regardless of the build system they're on.

I'm assuming you are referring to https://github.com/jart/sectorlisp which I gather is an attempt to make a Lisp that fits in a disk boot sector?

I think SIMD was a distraction to our conversation, most code doesn't use it and in the future the length agnostic, flexible vectors; https://github.com/WebAssembly/flexible-vectors/blob/master/... are a better solution. They are a lot like RVV; https://github.com/riscv/riscv-v-spec, research around vector processing is why RISC-V exists in the first place!

I was trying to find the smallest Rust Wasm interpreters I could find, I should have read the source first, I only really use wasmtime, but this one looks very interesting, zero deps, zero unsafe.

16.5kloc of Rust https://github.com/rhysd/wain

The most complete wasm env for small devices is wasm3

20kloc of C https://github.com/wasm3/wasm3

I get what you are saying as to be so small that there isn't a place of bugs to hide.

> “There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” CAR Hoare

Even a 100 line program can't be guaranteed to be free of bugs. These programs need embedded tests to ensure that the layer below them is functioning as intended. They cannot and should not run open loop. Speaking of 300+ reimplementations, I am sure that RISC-V has already exceeded that. The smallest readable implementation is like 200 lines of code; https://github.com/BrunoLevy/learn-fpga/blob/master/FemtoRV/...

I don't think Wasm suffers from the base extension issue you bring up. It will get larger, but 1.0 has the right algebraic properties to be useful forever. Wasm does require an environment, for archival purposes that environment should be written in Wasm, with api for instantiating more envs passed into the first env. There are two solutions to the Wasm generating and calling Wasm problem. First would be a trampoline, where one returns Wasm from the first Wasm program which is then re-instantiated by the outer env. The other would be to pass in the api to create new Wasm envs over existing memory buffers.

See, https://copy.sh/v86/

MS-DOS, NES or C64 are useful for archival purposes because they are dead, frozen in time along with a large corpus of software. But there is a ton of complexity in implementing those systems with enough fidelity to run software.

Lua, Typed Assembly; https://en.wikipedia.org/wiki/Typed_assembly_language and Sector Lisp; https://github.com/jart/sectorlisp seem to have the right minimalism and compactness for archival purposes. Maybe it is sectorlisp+rv32+wasm.

If there are directions you would like Wasm to go, I really recommend attending the Wasm CG meetings.

https://github.com/WebAssembly/meetings

When it comes to an archival system, I'd like it to be able to run anything from an era, not just specially crafted binaries. I think Wasm meets that goal.

https://gist.github.com/dabeaz/7d8838b54dba5006c58a40fc28da9...

Based on this, the next thing you wrote, and your reference to running a minimal Gentoo: I think you might be a Scheme fan in the making. Scheme is the minimal Lisp. (Okay, that might be sectorlisp which fits in 512 bytes.) It’s hands down my favorite language. While it’s evolved on its own to be more of a superset of Scheme, Racket is my Scheme of choice.

sectorlisp