@@ -10,7 +10,7 @@ option a) run the quickstart.sh script
option b) run the buildall.sh script, the examples can be found in the binaries directory
On other systems: Build glfw somehow (docs are in extern/gflw) and set up a build system manually.
On other systems: glfw is build with cmake.
Note:
* Make sure to use a different build directory for each example
...
...
@@ -18,6 +18,10 @@ Note:
-DCMAKE_BUILD_TYPE=Debug
to the cmake run to create a debug build.
If you encounter problems regarding missing c++11 features, you probably need to set the std lib variable. This is for example the case if you are using a clang version older than 3.3 (or Xcode 5.0). You can set this variable by uncommenting line 13 of shared/SharedCmakeLists.txt
If you encounter problems due to #version 130 not being supported in example 001-hello-world you might want to set ACGL_OPENGL_SUPPORT to CORE_32 and define ACGL_OPENGL_VERSION_32 . You will also have to change #version 130 to #version 150 in HelloWorld.fsh and HelloWorld.vsh
----------------
Note and TODOs
...
...
@@ -25,12 +29,12 @@ Note:
This repo differs in a few aspects from other ACGL template/example repos:
* extern/gflw is build via cmake, a shel script has to be used manually
* extern/gflw is build via cmake.
* extern/glfw is not a subrepository
* all other external libraries are compiled into the examples statically
* all examples share one repo
glfw is build with it's own complex build system, glfw 3 however will provide cmake files that will help setting up cmake files that are compatible with our build layout. Creating a new build system for glfw 2 might not be worth the effort, for glfw 3 you might want to wait for a final release.
glfw is build with it's own complex build system, glfw 3 however will provide cmake files that will help setting up cmake files that are compatible with our build layout.
As long as gflw can't be build with our build system, it should not get it's own git repository as all repos in the SDK should be buildable the same way.
