Results 1 to 2 of 2

Thread: Windows Calling Convention

  1. #1
    Senior Member
    Join Date
    Feb 2006
    Posts
    115

    Windows Calling Convention

    Hi,

    I was playing with the refenerce implementation of OpenVG, and ran into a little problem. As best as I can tell, the calling convention on the entry points is __cdecl (*not* __stdcall) on both the EGL and VG entry points. The same seems true for rasteroid, as well as amanithvg...

    Now, when running things like GLES applications under windows, I noticed that those expect the __stdcall calling convention for both EGL, and GLES.

    This makes things like putting EGL+VG+GLES in one driver seem rather difficult. Is the reference implementation wrong and should the entry points be defined as APIENTRY (== stdcall) for windows? Having it as anything else (like __cdecl) seems kind of silly to me.

    Thanks,

    Ivo

  2. #2
    Senior Member
    Join Date
    May 2006
    Posts
    353

    Re: Windows Calling Convention

    Quote Originally Posted by Ivo Moravec
    Now, when running things like GLES applications under windows, I noticed that those expect the __stdcall calling convention for both EGL, and GLES.
    That would depend on the egl.h/eglplatform.h/openvg.h/gl.h header files used when compiling those applications.
    Georg Kolling, Imagination Technologies
    Please ask questions specific to PowerVR hardware or SDKs on the PowerVR Insider Forum
    DevTech@imgtec.com | http://www.powervrinsider.com

Similar Threads

  1. Calling obsolete TexImage2d
    By TGlad in forum Developers Coding:Beginner
    Replies: 2
    Last Post: 07-21-2010, 02:46 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •