----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Jeroen Zwartepoorte" <[EMAIL PROTECTED]> Cc: "Gert Driesen" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, June 27, 2004 1:49 PM Subject: Re: [Nant-users] using pkg-config::get-link-flags in <csc> task
> Jeroen Zwartepoorte wrote: > > >I think Jareks suggestions is a bad idea: the whole point behind pkg- > >config is that *all* you need to know as a developers is the name of the > >package. You do not need to know where the packages reside (there are > >multiple locations configurable with PKG_CONFIG_PATH env variable) or > >which actual libraries a package needs. For example, gtk-sharp consists > >of the gtk-sharp.dll, gdk-sharp.dll, pango-sharp.dll etc. In a future > >release of gtk#, it'll probably add some more libraries (gnome-vfs- > >sharp.dll). You do not want application authors to have to deal with > >libraries/paths on their own. That's what got people to write pkg-config > >in the first place :) > > > ></rambling> > > > > > I tend to agree that supporting pkg references is a good thing becuse it > maps what the command line interface to mcs does and mono developers > will expect to be able to use them. Is it ok to start exposing the pkg-references element to build authors now ? Gert ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
