|
From: Ted G. <te...@go...> - 2012-04-03 03:51:39
Attachments:
signature.asc
|
So, I screwed up, but I want to try and help others! I wanted to use the valgrind macros in my application and I did what is typical of pkgconfig based projects and I just added valgrind to my list of pkgconfig files to check. This properly setup my include files and away I went. But, what it also did is linked my tests with a bunch of libraries that they didn't need to be. It seems to me that the valgrind pkgconfig file is serving two audiences, one is application folks (like myself). And the other is tool builders who need to link to the libs. Would you guys be interested in splitting this into two pkgconfig files? I'd propose valgrind.pc (for tools) and valgrind-apps.pc for application developers. I'm guessing more tools folks are using it today, and then they wouldn't have to change. Thoughts? Thanks, Ted |