Dependencies VS tsmp

I did some digging with Dependencies and found that issue is with libstdc++-6.dll

Maybe Dependency Walker can shed some light on that 🤔

I did that, basically. Problem is there is a clblast.dll (on windows) that llama.dll depends on, and it llama-cpp-python always failed dependency resolve to find it. I copied the dll to the right folder, loading it manually via CDLL worked fine, and https://github.com/lucasg/Dependencies also confirmed the dll was findable. When loading DLL's in windows, it checks the same folder for dependency dll's (and a few other places).

You can uses dependencies walker to detect the exact version of MS c++ runtime required.

If that doesn't work you will have to do it the hard way like i did. Using Dependencies to find the missing dlls

("Dependencies" is Dependencies.exe from https://github.com/lucasg/Dependencies)

If you're using MinGW or Cygwin and link in an arbitrary number of system libraries, then you need to ship those files as well. You can use Dependencies to list all DLLs your program is using, including transient dependencies.

A couple of them, yes. Someone else linked Dependencies which is much more modern and doesn't have some of the issues these older applications have. Thank you for the suggestions regardless.

I wrote a libclang based code generation tool and a support library to do static reflection and generate proxies for classes. You can check it out here https://github.com/fabian-jung/tsmp.

I'm trying to port my reflection library tsmp to windows and struggle linking the introspection tool to libclang-cpp and llvm. I tried different routes with no success so far.

I use an additional AST pass to generate type traits for static reflection. You can check it out here: tsmp

I'm happy to announce the first release of my meta-programming library tsmp. The library allows you to iterate through the public fields and functions of classes and the values of enumeration types. The reflection is enabled by parsing the source tree in the background and generating special type-traits that are consumed by the library. The big advantage is that you do not need to litter your code with macros and it does support custom types that are handed into your APIs from your users.

I'm working on a static reflection library called tsmp. It lets you iterate over structs and (typed) enums, as well as wrap class methods with proxies. The main goal is to be non intrusive (no macros) and i did it with the help of code generation in the background. I'm currently finishing a json helper and after that I'll polish the buildsystem and release the first version.

I tried basically the same with my introspection library here. Maybe we can join forces.

You can find the source code an the example in my repository here: https://github.com/fabian-jung/tsmp

A static reflection library for C++20. It is work in progress and feedback is very much appreciated. https://github.com/fabian-jung/tsmp