On 25/05/14 13:26, Dimitar Zhekov wrote:
On Sat, 24 May 2014 11:55:47 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On 18/05/14 19:08, Dimitar Zhekov wrote:
On Sun, 18 May 2014 15:30:21 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
On 16/05/14 18:41, Dimitar Zhekov wrote:
The prefix problem is workarounded. Since geany.pc is installed in \geany\path\lib\pkgconfig now, win32 pkg-config automatically uses /geany/path, replacing \ with / and ignoring the prefix setting. [...]
Not sure whether I completely understand the problem here.
With a prefix with backshahes in geany.pc (unlike the other variables, and any other .pc files), my gcc decides than c:\geany\path/include is c:geanypath/include. The same goes for c:\geany\path/lib et cetera,
Ah got it, finally :). Should be better in 1bacf869e076ef37caa768196d21d941a657d1e7,
Broke it completely. :)
Dammit, I was so sure we got rid of that problem now :).
I changed the code from hard-coded forward slashes to os.path.join(). Still, there are tons of forward slashes in the build system. If these cause problems at any stage, let me know.
Again: the problem is that the _backward_ slashes in the prefix (and now the other variables) in geany.pc are treated as escape characters by cpp, gcc or whatever. With geany.pc in "c:\what\ever\lib\pkgconfig" (in 1.24+), win32 pkg-config ignores $prefix and uses "c:/what/ever". That doesn't any more, because $includedir became "c:/what/ever\include", processed as "c:/what/everinclude" ("\i" does not stand for anything particular, thus simply "i").
The fix is to revert 1bacf869e076ef37caa768196d21d941a657d1e7. It would nice to have the prefix in geany.pc with forward slashes, but not really important - all glib/gtk+ .pc files contain prefixes like c:/devel/target/059c48de6b739307c37648aba3005b29, and pkg-config ignores them as described above.
Ok, in 01cf9a9fdc6795b971cbad59585d33bfcb796b74 I reverted the part of replacing forward by backward slashes for the geany.pc file. And additionally I added a little hack to replace \ by / for the prefix if on Windows.
I hope that actually really improves the situation. If not, I'd be happy to accept a patch to get it fixed :).
Regards, Enrico