Looking up libraries and header files

[Lowell Gilbert]

"David Southwell" <david at vizion2000.net> writes:

>  
>
>> -----Original Message-----
>> From: owner-freebsd-questions at freebsd.org 
>> [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of 
>> David Southwell
>> Sent: 01 October 2009 07:50
>> To: 'Mak Kolybabi'
>> Cc: freebsd-questions at freebsd.org
>> Subject: RE: Looking up libraries and header files
>> 
>>  
>> 
>> > -----Original Message-----
>> > From: owner-freebsd-questions at freebsd.org
>> > [mailto:owner-freebsd-questions at freebsd.org] On Behalf Of 
>> Mak Kolybabi
>> > Sent: 01 October 2009 07:07
>> > To: david at vizion2000.net
>> > Cc: freebsd-questions at freebsd.org
>> > Subject: Re: Looking up libraries and header files
>> > 
>> > On 2009-10-01 06:59, david at vizion2000.net wrote:
>> > > What is the simplest way to found out which port installs 
>> specific 
>> > > harder or library files?
>> > 
>> > pkg_info has a --which flag that tells you what package a file came 
>> > from:
>> > % pkg_info --which /usr/local/include/pcre.h 
>> /usr/local/include/pcre.h 
>> > was installed by package pcre-7.9
>> > 
>> > --
>> > Matthew Anthony Kolybabi (Mak)
>> > <mak at kolybabi.com>
>> Thanks Mat
>> 
>> Now I have two solutions for the  price of one question
>> 
>> Brill!!
> OK
>
> One problem 
>
> How about ports that are not installed?
>
> Is there another route that will deal with stuff not on the system?
>
> David

You can search the pkg-plist files in the ports tree.  This won't work
for ports that build a dynamic plist, but those are fairly unusual among
library ports.

-- 
Lowell Gilbert, embedded/networking software engineer, Boston area
		http://be-well.ilk.org/~lowell/