resolve relative include paths

[pierrec]

Currently, when integrating C libraries, the include paths must be absolute or the C compiler does not find them. It would be nice if So would resolve the relative include paths to the path where it temporarily builds the C files.

Example:
this fails as the included file is relative to the main.go location.

// main.go
package main

//so:include "lib3p/glfw/include/GLFW/glfw3.h"

[nalgeon]

You can add the necessary -I flags so the C compiler can find the header files. I'm not sure about the layout of your project, but if both main.go and lib3p are in the project root, and you are building from the project root too — you can just do this:

CFLAGS="-I." so build .

[pierrec]

Yes, this works but was thinking along the lines of your v0.3 link directive, which avoids using LDFLAGS.

[nalgeon]

The difference with LDFLAGS is that they don't depend on the project layout, unlike include paths. In your case, the include root, source root, and build root are all the same directory. But in other projects, these could be three separate directories, and I'd rather not try to guess the project layout in the transpiler.

[pierrec]

Agreed but I was expecting relative include paths to be resolved according to the file they are declared in. Not a big deal.

[pierrec]

FWIW claude also identified this as a gap while migrating my glfw/opengl pipeline to sokol.