CGO_CFLAGS multiple include paths on Windows

Technical Discussion
1

I’ve noticed something that may be a bug on Windows:

If I

export CGO_CFLAGS="-I/c/Users/travis/ffmpeg-4.2.2-win64-dev/include -I/c/Users/travis/openal-soft-1.19.0-bin/include"

my ffmpeg packages will build, but the openal stuff will complain about missing headers:

# golang.org/x/mobile/exp/audio/al
..\..\..\..\..\..\pkg\mod\golang.org\x\mobile@v0.0.0-20190719004257-d2bd2a29d028\exp\audio\al\al_notandroid.go:30:10: fatal error: AL/al.h: No such file or directory
 #include <AL/al.h>
          ^~~~~~~~~
compilation terminated.

If I invert the directives like this

export CGO_CFLAGS="-I/c/Users/travis/openal-soft-1.19.0-bin/include -I/c/Users/travis/ffmpeg-4.2.2-win64-dev/include"

then the opposite will happen:

# github.com/piepacker/wagashi/apps/sonic/ffmpeg
ffmpeg\error.go:8:11: fatal error: libavutil/error.h: No such file or directory
 // #include <libavutil/error.h>
           ^~~~~~~~~~~~~~~~~~~
compilation terminated.

It looks like the second include directive is always ignored.

2

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.