Khronos public bugtracker – Bug 651
Problems while building GTFfor GL and GLES20
Last modified: 2013-06-06 02:45:32 PDT
Hello, We are trying to build GTF framework on OpensUSE 11. For GLTARGET=GLES20 We are getting build failure.Problem with GLES20 is some of the GTF APIs were define only for GL as well as GLES30 not for GLES20 Here I am providing the problem with GLES20 yObject.o obj/GTFExtensionTestCompressedPalettedTexture.o obj/GTFExtensionTestReadFormat.o obj/GTFExtensionTestCompressedETC1RGB8Texture.o obj/GTFExtensionTestRGB8RGBA8.o obj/GTFExtensionTestStencil1.o obj/GTFExtensionTestStencil4.o obj/GTFExtensionTestVertexHalfFloat.o obj/GTFExtensionTestEGLImage.o -L. -Xlinker -rpath-link=/usr/lib -Xlinker -rpath-link=/usr/lib -lGL -lGLESv2 -lX11 -lEGL -o GTF -g -m32 -lm obj/GTFCoverageGL.o:(.rodata+0xcd4): undefined reference to `GTFTestCoverageGLCallUniform1i' obj/GTFCoverageGL.o:(.rodata+0xcdc): undefined reference to `GTFTestCoverageGLCallUniform2i' obj/GTFCoverageGL.o:(.rodata+0xce4): undefined reference to `GTFTestCoverageGLCallUniform3i' obj/GTFCoverageGL.o:(.rodata+0xcec): undefined reference to `GTFTestCoverageGLCallUniform4i' obj/GTFCoverageGL.o:(.rodata+0xcf4): undefined reference to `GTFTestCoverageGLCallUniform1f' obj/GTFCoverageGL.o:(.rodata+0xcfc): undefined reference to `GTFTestCoverageGLCallUniform2f' obj/GTFCoverageGL.o:(.rodata+0xd04): undefined reference to `GTFTestCoverageGLCallUniform3f' obj/GTFCoverageGL.o:(.rodata+0xd0c): undefined reference to `GTFTestCoverageGLCallUniform4f' obj/GTFCoverageGL.o:(.rodata+0xd14): undefined reference to `GTFTestCoverageGLCallUniform1iv' obj/GTFCoverageGL.o:(.rodata+0xd1c): undefined reference to `GTFTestCoverageGLCallUniform2iv' obj/GTFCoverageGL.o:(.rodata+0xd24): undefined reference to `GTFTestCoverageGLCallUniform3iv' obj/GTFCoverageGL.o:(.rodata+0xd2c): undefined reference to `GTFTestCoverageGLCallUniform4iv' collect2: ld returned 1 exit status Please kindly provide us the support while building it for GLES20 of GTF Thanks for the support. ~Rajesh.k
If this is still an issue, please raise it through internal Khronos mailing lists.