GNOME Bugzilla – Bug 378769
Should use mono-cairo.pc instead of -r:Mono.Cairo
Last modified: 2006-11-26 23:51:03 UTC
Hi, currently banshee uses -r:Mono.Cairo to link to the Mono.Cairo library. This won't work in some cases, for example if one compiles f-spot with gmcs but does not have Mono.Cairo 2.0 installed, only 1.0 which is completely valid. gmcs only looks in /usr/lib/mono/2.0, mcs in /usr/lib/mono/1.0 when doing -r:something. So specifying a complete assembly path is needed unless you really want the same version as your runtime is for. But in that case you should check for Mono.Cairo 2.0 in configure and use it's pkg-config file (that is not existant yet, bug filed at mono upstream). Bye
In Banshee, a 2.0 Mono.Cairo is checked at configure. -r:Mono.Cairo looks in the 2.0 GAC, so I'm really not sure what the problem is. Adding -pkg:Mono.Cairo when that's not even currently supported is out of the question I think. Can you maybe explain this a little better? How/where is this an actual issue, especially one that's considered "major".
Sorry, was caused by an mistake on my side. I should've checked it more before filing this bug :) But FYI -r:Mono.Cairo doesn't look in the GAC but /usr/lib/mono/2.0 with gmcs.