C89

[Honest Guvnor]

What are the views on writing the library in C89 to support cross platform projects? For example, the free native tools on Windows provide only C89 plus the odd extensions. This is an important platform for quite a few projects.

[Nicolas Rougier]

It is supposed to be written in C89. Do you mean you cannot compile it ?

Nicolas

On Jul 3, 2013, at 10:08 AM, Honest Guvnor <honest...@gmail.com> wrote:

What are the views on writing the library in C89 to support cross platform projects? For example, the free native tools on Windows provide only C89 plus the odd extensions. This is an important platform for quite a few projects.

--
You received this message because you are subscribed to the Google Groups "freetype-gl" group.
To unsubscribe from this group and stop receiving emails from it, send an email to freetype-gl...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Honest Guvnor]

Nicolas,

On 03/07/2013 10:51, Nicolas Rougier wrote:
>
> It is supposed to be written in C89.

My apologies for not reading the code properly. I had come to the
project via skimming 2 or 3 issues about Windows where the C seemed to
be compiled as C++ and was reading the font-demo program when I posted.

> Do you mean you cannot compile it ?

I have a few issues but, having already posted in haste, I will first
use it a bit before offering suggestions. Perhaps I am expecting the
library to be something you do not intend it to be.

Some of the issues:
- top level include files with names like opengl.h and vector.h
- including header files for opengl, glew,... For example, the
application code included gl headers before freetype-gl.h and so the
glew include failed.
- AntTweakBar handling in CMakeLists.txt seems broken if AntTweakBar is
absent
- missing __declspec(dllexport) guff for Windows
- shared libraries
- building freetype-gl from within a script requires cmake command lines
parameters not to be hard coded
- other packages used by an application, e.g. wxwidgets, qt, may also
include packages like freetype and have constraints on the version. The
cmake build script should handle this.
- missing cmake install
- build on Windows failed with a message about macros and missing
brackets. I stopped at this point on Windows. No problems on Linux.
Issue unresolved and might be due to problems controlling the Windows
environment when using multiple packages.

I shall probably rewrite the cmake file to use within my application and
post it to you with a bit of reasoning,

regards,

Andy.