<div class="gmail_quote">On Thu, Feb 18, 2010 at 5:06 PM, Thomas Moulard <<a href="mailto:thomas.moulard@gmail.com">thomas.moulard@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Thu, Feb 18, 2010 at 4:29 PM, Peter Johansson <<a href="mailto:trojkan@gmail.com">trojkan@gmail.com</a>> wrote: > Jeff Squyres wrote: >> Greetings. I'm creating .pc files for our project (<a href="http://www.open-mpi.org" target="_blank">www.open-mpi.org</a>). >> >> Where does one typically install these files? I see that pkg-config(1) v0.23 says: >> >> ...By default, pkg-config looks in the directory prefix/lib/pkgconfig for these files;... >> >> Does that really mean $prefix/lib/pkgconfig? Or does it actually mean $libdir/pkgconfig? >> >> > I use the latter: $(libdir)/pkgconfig Two usual cases which justify a custom libdir is: - release/debug libraries - different instruction sets (32/64 bits for instance) ...and in both case you really want to maintain two different sets of .pc files. So yes, IMHO $(libdir)/pkgconfig is the good solution. </blockquote><div> as $(libdir) can be modified by the user (it's a configure option), $libdir)/pkgconfig is the only reasonable solution. Vincent Torri </div></div>