On Fri, 4 Nov 2016, 8:36 AM Russ Cox <r...@golang.org> wrote: > We would like to fix the behavior of cgo invoking pkg-config on Windows, > for golang.org/issue/16455. From the failure in the report, it appears > that pkg-config --libs printed the actual text "C:/Program Files > (x86)/libgit2/lib" as part of its output, without any kind of escaping of > the spaces in that path. In contrast, the Unix pkg-config always escapes a > space with a backslash. We're trying to figure out whether there is some > commonly used Windows port of pkg-config that does escaping differently > and, if so, what the rules are. > > Does anyone use pkg-config on Windows? Can you see what output you get > from --cflags and --libs for any real library that you have installed in a > path with spaces? > > Thanks. > Russ >
I don't know if this is helpful, since I don't personally work in Windows, but Windows users of a binding I help maintain have had to deal with pkg-config as part of the process. Part of their proposed solution was using pkg-config lite? Thread here: https://github.com/gographics/imagick/issues/87 > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
