2 ms·
Good luck with getting pkg-config to recognize your include files automatically, for example. Or the good old "man" utility. Alternative: maintain a HUUUUUGE l
by mschuster91 10y ago
Good luck with getting pkg-config to recognize your include files automatically, for example. Or the good old "man" utility.
Alternative: maintain a HUUUUUGE list of xPATH env variables, and update them every time you recompile something and change the directory in the process. Oh, and hope that other people's Makefiles are intelligent enough to not mess up shit (e.g. use headers from system, and library .so files from your own compile)...
- vog 10y agoIf you are alluding to cross-compiling, rest assured that I wrote my comment being fully aware of the plenty of pitfalls, which is why I started the MXE (mingw-cross-env) project some time ago: http://mxe.cc/ http://mxe.cc/
- mschuster91 10y agoCross-compiling is yet another pile of dungheap in addition to the dungheap I mentioned. I usually set up a Debian chroot with qemu and compile "natively" (e.g. for RPi). It's dog slow, yes, but at least it works reliably in contrast to cross compilation. The only way I ever got CC to work is with the buildroot toolchain, which has the downside that it isn't Debian.