Bug 32948 - parts of openTK inside xamarin.mac.dll
Summary: parts of openTK inside xamarin.mac.dll
Status: RESOLVED ANSWERED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Library (Xamarin.Mac.dll) ()
Version: 2.0.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2015-08-11 05:50 UTC by renan jegouzo
Modified: 2015-09-29 15:06 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED ANSWERED

Description renan jegouzo 2015-08-11 05:50:09 UTC
parts of OpenTK are include inside Xamarin.Mac.dll
cause of that we can't link with a newer  OpenTK, that supports OpenGL 4, etc..
and we are stuck with the old open TK shipped with xamarin.
Comment 1 renan jegouzo 2015-08-11 06:07:47 UTC
also can'f find where is located OpenTK.Graphics.GraphicsContext in xamarin.mac.dll
Comment 2 renan jegouzo 2015-08-11 06:09:11 UTC
and without GraphicsContext it's impossible to make multithreaded OpenGL renderer
Comment 3 renan jegouzo 2015-08-11 06:16:45 UTC
it's worst than that, just a small part of OpenTK is include, and impeach to link with OpenTK..
Comment 4 renan jegouzo 2015-08-11 06:27:37 UTC
I found the problem, xamarin.mac mobile include opentk, but opentk is missing in xamarin.mac 4.5 (supported version)
Comment 5 renan jegouzo 2015-08-11 06:29:06 UTC
kist the openTk maths are include that impeach to link with our own openTK
Comment 6 renan jegouzo 2015-08-11 06:37:04 UTC
to resume;

using xamarin.mac mobile, it's possible to reference the provided OpenTK, but it can't be used cause of the missing System.drawing, and that we can't reference other libraries.

using xamarin.mac 4.5 (supported) , system.drawing is available, parts of OpenTK are include directly in xamarin.mac, but the real OpenTK isn't provided, and it's not possible to link with a third party OpenTK cause of included parts (vector, matrix, etc..)
Comment 7 renan jegouzo 2015-08-11 06:44:27 UTC
I need to use xamarin mac with my own OpenTK
Comment 8 renan jegouzo 2015-08-11 06:45:52 UTC
and not your broken old one
Comment 9 renan jegouzo 2015-08-11 07:21:59 UTC
I don't understand, if you want to build an unified API, why you didn't kept the same OpenTK for xamarin.mac than on linux, monomac, ios and android..
Comment 10 renan jegouzo 2015-08-11 07:25:03 UTC
it was the only graphics part that was unified already... :/
Comment 11 renan jegouzo 2015-08-11 08:47:21 UTC
please stop making new broken things and fix old ones, xamarin is always unusable for real projects cause of untested modifications... and ship the missing OpenTK library for net 4.5.. and please remove the parts of OpenTK included in Xamarin.Mac.
Comment 12 renan jegouzo 2015-08-11 10:22:28 UTC
Ok, GraphicsContext isn't necessary with the xamarin.mac mobile framework OpenTK, as it works without the needs of dummy openTK context.. 

finally, the only problem I found was the missing missing OpenTK library in net45. and a problem with GL.DeleteProgram (I filled a new bug report)

if OpenTK working, I don't care so much to not using my own OpenTK...
Comment 13 Chris Hamons 2015-09-29 15:06:15 UTC
I'm having trouble following your bug, but it sounds like it is resolved. Please open a new bug and clearly describe the problem (preferably with an example showing the issue) if it still exists.