By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,403 Members | 1,359 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,403 IT Pros & Developers. It's quick & easy.

Mono.Cairo in C# WIN32 app

P: n/a
Hi to all!

Any of you know if it's possible to use the Cairo graphics library in
a WIN32 c# application? I know there is a binding made for Mono but my
app will run on win32 so obviously I wont need Mono.

Any help will be appreciated. Thanks!
Oct 8 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
flagos wrote:
Any of you know if it's possible to use the Cairo graphics library in
a WIN32 c# application? I know there is a binding made for Mono but my
app will run on win32 so obviously I wont need Mono.
Why exactly have you picked Cairo as opposed to Windows.Forms, WPF or Gtk#?
Bindings for those are readily available.

AFAICT there is no pre-built .NET wrapper for Cairo outside of Mono. It's
probably possible to extract and adapt Mono.Cairo for the Microsoft CLR. If
you're lucky it's purely managed without dependencies on other parts of
Mono, in which case you don't need to change anything at all and the
assembly will just work for any .NET application. If you're slightly less
lucky there will be some dependencies with other Mono code, and if you're
very unlucky it will integrate with unmanaged parts of the Mono CLR. I'd be
surprised if that were the case, though.

Should all this be too much trouble, you could always write your application
for Mono anyway. Mono runs on Win32 just fine, and just because you don't
need your application to be portable doesn't mean it *musnt't* be either.

--
J.
Oct 8 '08 #2

P: n/a
Thanks for your answer!
Why exactly have you picked Cairo as opposed to Windows.Forms, WPF or Gtk#?
I'm looking for a 2d drawing/visualization engine. Not a GUI toolkit.

Regards.

Oct 8 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.