#7 Open
Repository
urkle
Branch
feat-gles
Repository
alfonse
Branch
default

Bitbucket cannot automatically merge this request.

The commits that make up this pull request have been removed.

Bitbucket cannot automatically merge this request due to conflicts.

Review the conflicts on the Overview tab. You can then either decline the request or merge it manually on your local system using the following commands:

hg update default
hg pull -r feat-gles https://bitbucket.org/urkle/glloadgen
hg merge feat-gles
hg commit -m 'Merged in urkle/glloadgen/feat-gles (pull request #7)'
Author
  1. Edward Rudd
Reviewers
Description

Here is my initial stab at adding in GLES support to glLoadGen. I added two new spec otion values.. gles1 and gles2. The reason is the way the spec is defined it isn't "core" and "compatible".. GLES 1.x is fixed-function ONLY, GLES 2.x+ is shader ONLY. the spec files were generated via your XMLSpecs repository with very minimal changes. (I'll push up a PR for that next)

there are a few other items that got snuck in here as spearate commits.. I can put those as separate PRS if you wish.

First is the is the addition of the SDL Function loader. This is also used in the GLES1/2 loaders right now.. I'll adjust that in a bit once I finish testing on iOS and Android. Second is the tweak to support Lua 5.3

  • Add in SDL2 GetProcAddress support to the GL loader.
  • add in generated GLES spec files for ES 1.x, 2.x and 3.x
  • Adjust core lua scripts to support generating GLES 1.x adn GLES 2.x+ loaders
  • update hgignore and tweak GenTests/MakeAllExts for GLES
  • add in Lua 5.3 support unpack is fully moved to table.unpack so create a wrapper in util

Comments (2)

  1. Erik Podetti

    I'm really interested in generating Open GL ES 3.2 headers in cpp style (with namespace and so) because I'm using glLoadGen in a multi platform project. Can you give me an example on how to generate them with your branch?