Menu
▾
▴
1 Attachments
#286 Detect ncurses flags using pkg-config with fallback
This addresses bug #476. On some systems like Gentoo, simply using -lncurses isn't enough because the tinfo symbols are in a separate library. pkg-config allows the build to work out of the box even on some fairly exotic systems, assuming they have .pc files present, which many do these days. I have also included a fallback to the old mechanism and tidied up the logic a bit.
This goes unfortunately wrong with my cross-compiler, as there the pkg-config of the host used to to find curses, ending up with the wrong file.
should I specify some flag to not use pkg-config or is it a weird case that the cross-compiler doesn't have it while the host has.
Cross-compile environments vary so I guess there is no standard approach for this but Gentoo installs a wrapper script such as
/usr/bin/m68k-unknown-linux-gnu-pkg-configthat sets environment variables before callingpkg-config. I believe this is script is searched for automatically byconfigurebefore falling back to plainpkg-configbut you can also set the environment variables manually. For example:You may also need to set
PKG_CONFIG_SYSTEM_LIBRARY_PATHif your cross system has non-standard lib directory names such as/usr/lib64:/lib64.I found that cross-compiling worked for me even without doing the above for a few reasons. pkg-config will not normally include flags for standard paths like
/usr/includeand/usr/lib. This is controlled byPKG_CONFIG_SYSTEM_LIBRARY_PATH. Myncurses.pcdoesn't reference any other paths becausecurses.handncurses.soare in these standard paths. A cross toolchain will normally look under an alternative sysroot such as/path/to/cross/systemrather than just/so it will find the right files anyway if there are no-Ior-Lflags to throw it off.If your cross toolchain's default sysroot doesn't point to where your cross system is then you can override this with the
--sysrootflag. I find this works most effectively when appended toCCandCXX. For example:Please let me know if you have any more questions. Cross-compiling is a hobby of mine.
Under my cross-compiler the pkg-config stuff does not exist (the program itself doesn't). So it should not run pkg-config at all. the fallback finds the wrong library (name wise) and in the wrong place and of course the wrong OS.
You don't need the pkg-config binary installed in the cross system. It's a native binary so it wouldn't run anyway. Ideally you would have .pc files present there as they really do help, despite some of the FUD I've read around this in the past.
It's not essential though. I'm not forcing you to use pkg-config here. If you set
PKG_CONFIG_SYSROOT_DIRandPKG_CONFIG_PATHas above, even if there are no .pc files present then that will prevent pkg-config prevent picking up the ones on your build system... almost. When trying this out, I found that you have to setPKG_CONFIG_LIBDIRto either the same value asPKG_CONFIG_PATHor the empty string. I'm not sure why pkg-config has two variables for this but hey, it works.Actually another even simpler alternative if you really don't want to use pkg-config at all is to simply set this when calling configure.
You are not forcing me, but I do have to employ work arounds in order to be able to keep compiling dosbox. (which isn't that surprising in cross compilation setup). I don't know if pdcurses has pc files at all (as this is cross compiler on linux for windows)
I will give the variables a try, but it is a bit messy in case there are packages in my cross compiler that can be detected that way. (not that we use pkg-config anywhere else in dosbox, so for now it is not a real issue, but it is something to keep in mind when deciding if we want to add a package using it (and if we would be adding pkg-config at all))
The patch above no longer applies to the latest trunk so here's a new one. Please take this so that we don't have to keep fixing it.