Hello folks, I'm currently using libtcc inside a C++ application to compile, link and execute generated code. The generated code uses some smaller C library that gets compiled as part of the generated code (so basically C files which are being fed into libtcc Therefore, I'm using tcc_add_include_path(). The problem I'm having is that tcc_add_include_path() and tcc_add_library_path() only work for me for as long as those paths are absolute. However, as I want to deploy/distribute the program inform of a pre-built binary with the corresponding libtcc.dll (or libtcc.a / libtcc.so) along I need those paths to be relative. I had no luck getting that working what so ever. Unfortunately, I didn't find much in terms of documentation. I assume that the paths supplied are relative to the binary which contains/uses libtcc - is that correct? Is there any way to debug this? Is there anything obvious that I'm missing?
Best regards, ~ Joel _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
