After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 594662 - Getting an error when buiding PrintNotes addin on the Mac
Getting an error when buiding PrintNotes addin on the Mac
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
0.15.x
Other Mac OS
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-09-09 16:13 UTC by mohan
Modified: 2010-10-18 10:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Changes Tomboy/Addins/PrintNotes/PrintNotes-mac.csproj after chaging the reference to Mono.dll version 2.0 (1020 bytes, application/octet-stream)
2009-09-09 16:13 UTC, mohan 		Details

Description mohan 2009-09-09 16:13:15 UTC 
Created attachment 142803 [details]
Changes Tomboy/Addins/PrintNotes/PrintNotes-mac.csproj after chaging the reference to Mono.dll version 2.0

The error is as follows:

/Users/mohan/Projects/tomboy/Tomboy/Addins/PrintNotes/PrintNotesNoteAddin.cs(314,25):
error CS0029: Cannot implicitly convert type `Cairo.Context' to `Cairo.Context'

Looking at the compile options it seemed that it was using version 1.0 of the
Cairo.dll. 

After I changed the reference for the PrintNotes-mac solution via the Project >
Edit references  menu in MonoDevelop - it was referencing Mono.Cairo 1.0, I
changed it to reference version 2.0 and removed the reference to version 1.0, 
building it worked. The resulting diff of this change is attached with this
ticket.
Comment 1 Sandy Armstrong 2009-12-05 14:28:38 UTC 
I pushed your project file fix to git master, but have not tested it yet.

Please let me know if the problem remains for you.
Comment 2 Stefan Schweizer 2010-10-18 10:28:22 UTC 
I am closing this bug because the PrintNotes addin builds fine for me and printing (to a file) also works. Please feel free to reopen this bug if the problem remains for you.