[vtk-developers] bug 8513, updating freetype; need Windows dev to help

Bill Lorensen bill.lorensen at gmail.com
Fri Dec 11 13:14:40 EST 2009


Sean,

Sorry, I looked at the wrong VTK version. Here are the comments:

/*

VTK_FREETYPE_CHANGE this file is new for VTK.

This header file mangles all symbols exported from the freetype library.
It is included in all files while building the freetype library.  Due to
namespace pollution, no freetype headers should be included in .h files in
VTK.

The following command was used to obtain the symbol list:

nm libvtkfreetype.a |grep " [TRD] "

This is the way to recreate the whole list:

nm bin/libvtkfreetype.a |grep " [TRD] " | awk '{ print "#define "$3"
vtk_freetype_"$3 }'

In fact, you must do this on all supported platforms and merge the results,
since some symbols may be present on only some platforms.

Then alphabetise the list so that future diffs/merges work better.

Note that _fini and _init should be excluded because they are not functions
implemented by the library but are rather created by the linker and
used when the shared library is loaded/unloaded from an executable.

*/

I'm still surprised you need to do this on all platforms. But I have
not looked at freetype's internals.

Bill

On Fri, Dec 11, 2009 at 1:01 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> Sean,
>
> Here are the comments in my mangle file:
> /*
>
> VTK_FREETYPE_CHANGE this file is new for VTK.
>
> This header file mangles all symbols exported from the freetype library.
> It is included in all files while building the freetype library.  Due to
> namespace pollution, no freetype headers should be included in .h files in
> VTK.
>
> The following command was used to obtain the symbol list:
>
> nm libvtkfreetype.a |grep " [TRD] "
>
> This is the way to recreate the whole list:
>
> nm bin/libvtkfreetype.so |grep " [TRD] " | awk '{ print "#define "$3"
> vtk_freetype_"$3 }'
>
> */
>
> I don't see windows mentioned here.
>
> On Fri, Dec 11, 2009 at 12:45 PM, Sean McBride <sean at rogue-research.com> wrote:
>> On 12/11/09 12:16 PM, Bill Lorensen said:
>>
>>>I think the entry points from unix are sufficient. Why do you think
>>>you need windows entry points?
>>
>> The comments in vtk_freetype_mangle.h say it is necessary.  I think I
>> added that comment, but don't recall why.  I can't find the answer in my
>> email archives either.  But I've updated freetype several times in the
>> past, and it always (temporarily) breaks the dashboard, so trying a
>> different OS/compiler before I commit would be nice regardless.
>>
>> --
>> ____________________________________________________________
>> Sean McBride, B. Eng                 sean at rogue-research.com
>> Rogue Research                        www.rogue-research.com
>> Mac Software Developer              Montréal, Québec, Canada
>>
>>
>>
>



More information about the vtk-developers mailing list