Are libEGL.dll and libGLESv2.dll transferable to other development machines?

This topic contains 2 replies, has 2 voices, and was last updated by  kagha 3 years, 4 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #31740

    kagha
    Member

    Hello,

    I am currently developing some PowerVR based graphical software in a Windows environment. I make heavy use of libEGL.dll and libGLESv2.dll from the PowerVR SDK for testing in Windows.

    I have discovered that moving these DLL files form one Windows development machine to another results in undefined behavior (crashing & runaway memory consumption).

    I would like to know what is the consensus on PowerVR development regarding the distribution of these DLL files among internal team development machines.
    Are these files generated when the PowerVR SDK is installed and are indeed machine specific?
    If not can I just include them as part of my project in my source code repo?

    Any help is greatly appreciated.

    #38835

    Joe Davis
    Member

    Hi,

    The PVRVFrame library binaries are packaged with the SDK. They are not platform specific, so they should work when used on different development machines. Emulation requires a host OpenGL graphics driver that meets PVRVFrame’s minimum requirements. The PVRVFrame webpage overviews the requirements for each supported OpenGL ES API: https://community.imgtec.com/developers/powervr/tools/pvrvframe/

    Distributing the PVRVFrame emulation libraries with your application is ok as long as you adhere to the terms of our SDK End User Licence Agreement: https://community.imgtec.com/developers/powervr/sdk-end-user-licence-agreement/

    Regards,
    Joe

    #38836

    kagha
    Member

    Joe, Thank you very much for the timely and complete response. Your help is invaluable and very appreciated.

    Karim

Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.