2011/4/6 Fridrich Strba
Maarten,
On 05/04/2011 23:11, Maarten Bosmans wrote:
BuildRequires: pkgconfig (most common) BuildRequires: pkg-config (e.g. mingw32-cairo)
These two are equivalent because OBS takes care of renaming in the spec file either of them to the name the pkg-config package has in the distribution. These are normal native linux pkg-config packages that don't know about our /usr/i686-w64-mingw32/sys-root/mingw/lib/pkgconfig and /usr/i686-w64-mingw32/sys-root/mingw/share/pkgconfig directories unless one sets a special PKG_CONFIG_PATH. Which we do in the environment creation script, so that the mingw32-configure and other wrappers will set that variable. The disadvantage of this is that if you don't have on the system in the cross-compiling sysroot the given package, it will pick the native one if it is present. Which is not good
BuildRequires: mingw32-cross-pkg-config (e.g. mingw-poppler)
This is also a Linux native binary, although it is configured so that it knows only about our cross-compiling paths. It will not consider the native paths unless one adds them using the PKG_CONFIG_PATH variable. It is also installed as i686-w64-mingw32-pkg-config. The advantage is that if present, the environment creation script will set the PKG_CONFIG variable to it. Which means that the different configure scripts will use it. This is the preferable dependency,since it depends on the native pkg-config/pkgconfig anyway for the pkg.m4 macro file which this package does not install to avoid conflicts.
I hope I did not mess you up too much with this explanation
Thanks for the explanation. If I understand correctly, the second (preferred) option is like setting PKG_CONFIG_LIBDIR to the mingw32 specific directories instead of PKG_CONFIG_PATH.
F.
Can you then explain what the mingw32-pkg-config provides? Maarten -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-mingw+help@opensuse.org