Jeroen Zwartepoorte wrote:
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.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>
However its still just a convenience. Saying that app aothors shouldn't have to deal with libraries/paths is a bit of a stretch.
Ian
Jeroen
On Sun, 2004-06-27 at 17:41 +0900, Ian MacLean wrote:
Gert Driesen wrote:
ok but auto-quoting in all cases sems like the wrong thing to do. A user can always add quotes if necessary but they can't remove what we add automatically.----- Original Message ----- From: "Ian MacLean" <[EMAIL PROTECTED]> To: "Jeroen Zwartepoorte" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, June 25, 2004 4:25 PM Subject: Re: [Nant-users] using pkg-config::get-link-flags in <csc> task
ick -- I think that automatically quoting the values of <arg> elements
is being a bit too clever. I've made a change so that it will only
happen if those values are file paths. That change should come thru in
the next nightly build.
We'll need to double check if this doesn't cause any regressions, as some tasks might rely upon this behaviour ...
it would be nice to support pkg references directly. I guess we still need to make a dscision between doing that or using Jareks suggestion [1] to add package directories to our assembly resolution paths.Gert has also done some work integrating package references directly
into the compiler tasks. Its disabled for now as there was some pending
discussion on how to proceed with it. To enable it just uncomment line
249 of compilerbase.cs
//[BuildElement("pkg-references")] and you should be able to use pkg
references directly.
Ian, what's your opinion on this topic ?
[1] http://www.mail-archive.com/[EMAIL PROTECTED]/msg04157.html
-------------------------------------------------------
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
--
Ian MacLean, Developer, ActiveState, a division of Sophos
http://www.ActiveState.com
-------------------------------------------------------
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
