On Fri, Dec 3, 2010 at 11:22 PM, Roger Leigh <rle...@codelibre.net> wrote: >> > The header is just a text file. It doesn't contain any library >> > dependency information (or version information) at all, and there's >> >> boost/version.hpp > > We only care about SONAME versions, not release versions, and we only > need to care about what is available to the linker, and headers aren't.
The header file forwards it to the link via the pragma. >> > no way to associate a given header with any shared library at all. >> >> boost\filesystem\v3\config.hpp >> boost/config/auto_link.hpp > > These are using proprietary vendor-specific #pragmas. It's pretty True, but IMO the concept seems pretty useful. Why do you think it's horrible? It appears to work well. > horrible, not to mention fragile--if any header fails to include the > correct bits of magic, it all falls apart. If they had spent just > a fraction of the time implementing that to support pkg-config, we > wouldn't have a problem. g++ and MSVC don't use pkg-config (AFAIK). So the complexity is pushed down instead of up. > OTOH, that mechanism could feasibly be adapted to report the > library dependencies of the headers to auto-generate the necessary > pkg-config files, should anyone have the time to implement that > in auto_link.hpp and write a few tiny programs to spit out the > information. Olaf -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiktqy+agsilhkxxvaw_a7yr0warqz+ykgsgc...@mail.gmail.com
