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, 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. Some applications can handle the forward slashes even on Windows, others not. And IIRC also Windows sometimes handle the forward slashes properly, sometimes not. The correct thing would be to use os.path.join() everywhere but this would make the wscript way harder to read, this is why I tried to avoid this.
In the .pc file, the include paths at the end still use forward slashes, these are hardcoded in geany.pc.in template. Could you check whether this causes problems as well, if so, we would need to find a solution for this.
We discussed this briefly, but that was nearly a year ago ("Geany 1.23 Waf install under win32"), and apparently didn't happen on your system.
Yeah, it did not happen for me because I never used a "real" prefix, I always use the default "geany-$VERSION" without an any path components and so I never realised what you noticed.
The plugin installation, however, creates a \lib directory on the installation drive, with all lib<pluginname>.dll.a files
I'll post soon a tutorial how I build the release binaries on Windows. Apart from this, the whole build stuff on Windows is quite fiddled and I never considered it production-ready.
Once the X:\lib problem is fixed, it'll be fine, unless one decides to move geany.pc to another location. Will be be nice to have the same
Yeah but I don't know yet where this path (\lib) is set in Waf and how to change it. I didn't consider it a real problem yet apart from the fact that it sort of clutters the file system. I might will have a look at it if time permits.
Regards, Enrico