id summary reporter owner description type status priority milestone component version resolution keywords cc device_name 232 ffado-diag: don't use pkg-config to get package info ericboon arnonym pkg-config only works for development libraries, so this is not the correct way to determine whether a certain (non-dev) library is installed on a user's system.\r\n\r\nFrom the ffado-user mailing list:\r\n> From: _arnold@arnoldarts.de [[BR]]\r\n> Subject: _Re: [FFADO-user] [I'm a user and need support] JACK doesn't see PHASE X24 [[BR]]\r\n> Date: _September 13, 2009 7:07:50 PM GMT+02:00 [[BR]]\r\n> To: _ffado-user@lists.sourceforge.net [[BR]]\r\n> [[BR]]\r\n> On Sunday 13 September 2009 16:06:54 Eric Boon wrote:\r\n>\r\n>> Following up on my own mail, regarding ffado-diag: \r\n>>\r\n>>> I also tried 'ffado-diag', but the output of that one was rather\r\n>>> confusing. It complained about a number of packages not being\r\n>>> installed although they are there.\r\n>>\r\n>> That's because there's no package information stored. ffado-diag tries\r\n>> to get the info via pkg-config, but of all the packages installed on\r\n>> my system, only 5 or so actually shipped with the info that pkg-config\r\n>> reads. Ergo: pkg-config is not a reliable way to detect whether\r\n>> certain libs are installed or not - at least not on Debian.\r\n>\r\n> That is because the *.pc files are in the development packages as it is meant \r\n> for development. Probably not a good idea to check for libraries on a user-\r\n> system with a tool that "only" gives library-and include-paths for devs.\r\n bug closed minor FFADO 2.0 FFADO SVN (trunk) fixed