View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012636ParaView(No Category)public2011-10-10 09:402012-02-08 17:25
ReporterDavid Partyka 
Assigned ToDavid Partyka 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version3.10 
Target Version3.12Fixed in Version3.12 
Summary0012636: fix incompatibility with OCCT 6.5.2
DescriptionHere is a short description of the problem (I was reported on it in one of my previous mails).

The problem is that VTK embeds statically own patched versions of freetype and ftgl libraries (used to draw fonts). The freetype library (v2.4.4) is embedded in a proper way - to avoid any problems with external freetype, VTK uses special mangling of the symbols exported by freetype: all functions are renamed, and the library is named libvtkfreetype.
However, this is not done in the same way with ftgl. The VTK provides internal libvtkftgl library that is a patched version of ftgl v1.32.
Since version 6.4, OCCT also uses freetype / ftgl for the font drawing. However, OCCT uses these libraries by dynamic linking, moreover it uses newer versions (freetype 2.3.7 and ftgl 2.1.2). This raises compatibility problem since SALOME becomes linked to two different versions of ftgl! This causes crash in SALOME run-time when drawing fonts (for example, when displaying any mesh group in VTK viewer).

The only solution I could find is a creation of a patch for Paraview / VTK. In order to avoid problem with symbols tables, all ftgl classes (of internal libvtkftgl used in Paraview) are wrapped to the namespace. This allows using different mangling for the symbols. I have quickly tested resulting patch and did not found problems for the moment.

Also, this patch is compatible with Paraview 3.12rc2. Probably, it is good idea to send this patch to Kitware to include it in the final Paraview 3.12. EDF as a Kitware customer can forward this mail to the Paraview development team.

Also, there's an additional point about building OCCT 6.5.2 and its pre-requisites on 64bit platforms. For 64bit platforms CFLAGS="-fPIC -m64" configure option should be used. Please find updated OCCT_building.pdf attached (see p 2.3.7).
TagsNo tags attached.
ProjectTBD
Topic Name12636-fix-occt-incompatibility-6.5.2
Typeincorrect functionality
Attached Filestgz file icon PARAVIEW-3.10-PATCH.tgz [^] (6,975 bytes) 2011-10-10 09:42

 Relationships

  Notes
(0027614)
David Partyka (developer)
2011-10-26 15:53

 Merged into next 10/26/2011
(0027617)
David Partyka (developer)
2011-10-27 16:25

 Merged into master 10/27/2010 after some Windows additional fixes.
(0028146)
Utkarsh Ayachit (administrator)
2012-02-08 17:25

 Closing bugs sitting in "customer review" for a long time.

 Issue History
Date Modified Username Field Change
2011-10-10 09:40 David Partyka New Issue
2011-10-10 09:40 David Partyka Assigned To => David Partyka
2011-10-10 09:41 David Partyka Target Version => 3.12
2011-10-10 09:42 David Partyka File Added: PARAVIEW-3.10-PATCH.tgz
2011-10-10 09:58 David Partyka View Status private => public
2011-10-21 14:29 David Partyka Status backlog => todo
2011-10-21 14:29 David Partyka Status todo => active development
2011-10-26 15:53 David Partyka Topic Name => 12636-fix-occt-incompatibility-6.5.2
2011-10-26 15:53 David Partyka Note Added: 0027614
2011-10-26 15:53 David Partyka Status active development => gatekeeper review
2011-10-26 15:53 David Partyka Fixed in Version => 3.12
2011-10-26 15:53 David Partyka Resolution open => fixed
2011-10-27 16:25 David Partyka Note Added: 0027617
2011-10-27 16:25 David Partyka Status gatekeeper review => customer review
2012-02-08 17:25 Utkarsh Ayachit Status customer review => closed
2012-02-08 17:25 Utkarsh Ayachit Note Added: 0028146

Copyright © 2000 - 2018 MantisBT Team