Dear Riccardo, At Sat, 05 Feb 2011 00:35:26 +0100, Riccardo Mottola wrote: > > Hi, > > Riccardo, > > > > When other packages are compiled, I'm guessing that they use the > > pkg-config process. Your package probably installed a binary called > > libpng-config -- or likely libpng15-config. Doing things like > > "libpng-config --libs" will spit out the correct linking parameters > > for gcc, likewise for "libpng-config --cflags." > > > I'm not thinking about other packages provided by pkgsrc, but generally > programs supplied with sourcecode. > > The code may include <libpng/png.h> and generally link with -lpng, > configure will check for some locations but the structure is this usual > one. NetBSD used to comply to this too by providing some links. I think > it is a bug that the current libpng install is not done in this way > anymore, but perhaps it was done with some good reason? it might be the easiest to create /usr/pkgsrc/riccardo/xyzprogram and then to create a pkg there for the program you wish to install. While getting a program to compile in the pkgsrc framework has some overhead you save on some other tasks where pkgsrc just does the right thing. The few times I have installed a program _not_ using pkgsrc, I ended up regretting it later. I hope this helps. Best regards, Marko
Attachment:
pgp2L3Ybl1AkK.pgp
Description: PGP signature