[vtk-developers] Building VTK Master (8.90)

[Andrew Maclean]

Ben what you have done is outstanding!!!! +1

Ok on Ubuntu 18.10 I get a clean build now with these conditions.

I have local installations of Java 11.0.1, Anaconda Python 3.7.1 and TBB.
CMake found the Anaconda Python release library Ok, Java Ok, TBB Ok

Building with just the defaults and these changes:

VTK_ALL_NEW_OBJECT_FACTORY ON
VTK_ENABLE_GROUP_QT                WANT
VTK_JAVA_SOURCE_VERSION         1.9
VTK_JAVA_TARGET_VERSION          1.9
VTK_WRAP_PYTHON                          ON
VTK_PYTHON_VERSION                     3
VTK_SMP_IMPLEMTATION_TYPE      TBB
VTK_WRAP_JAVA                                 ON
VTK_WRAP_PYTHON                          ON

Then:
1) Manually set PYTHON_EXECUTABLE to
/home/<user_name>/anaconda3/bin/python3.7m
     Note: This is found in Ungrouped Entries
2) Set Java source/target versions to 1.9 (The wrapping doesn't know about
version 1.11)
3) TBB:
   In TBB_LIBRARY_DEBUG change libtbb_debug.so to libtbb_debug.so.2.
   In TBB_LIBRARY_RELEASE change libtbb.so to libtbb.so.2.
4) Add -luuid to CMAKE_CXX_FLAGS

Final result:
99% tests passed, 1 tests failed out of 2010

The following tests FAILED:
        293 - VTK::IOExportPDFCxx-TestPDFTransformedText (Failed)
Errors while running CTest

vtkpython works:
Python 3.7.1 (default, Dec 14 2018, 19:33:21)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> exit()

Regards
   Andrew

On Sun, Jan 13, 2019 at 10:03 AM Andrew Maclean <andrew.amaclean at gmail.com>
wrote:

> Also fixed the errors:
>     usr/bin/ld: /usr/lib/x86_64-linux-gnu/libSM.so: undefined reference to
> `uuid_unparse_lower at UUID_1.0'
>     /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libSM.so: undefined reference
> to `uuid_generate at UUID_1.0'
>
> by adding -luuid to CMAKE_CXX_FLAGS
>
> Regards
>    Andrew
>
>
> On Sun, Jan 13, 2019 at 8:39 AM Andrew Maclean <andrew.amaclean at gmail.com>
> wrote:
>
>> Thanks for that advice.
>> FYI: The PYTHON_EXECUTABLE:FILEPATH is in Ungrouped Entries.
>>
>> Regards
>>    Andrew
>>
>> On Sun, Jan 13, 2019 at 2:05 AM Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>
>>>
>>>
>>> On Sat, Jan 12, 2019 at 1:23 AM Andrew Maclean <
>>> andrew.amaclean at gmail.com> wrote:
>>>
>>>> In summary, I get a build on Ubuntu 18.10 with just the defaults and
>>>> these changes:
>>>> VTK_ENABLE_GROUP_QT->WANT
>>>> VTK_MODULE_ENABLE_VTK_RenderingFreeType DEFAULT->NO
>>>> VTK_WRAP_PYTHON on
>>>> VTK_PYTHON_VERSION 3
>>>> VTK_SMP_IMPLEMENTATION_TYPE TBB
>>>>
>>>> In VTK/lib there is a python2.7 folder. Given that I built for Python
>>>> 3.7.1, is this folder name correct?
>>>>
>>>
>>> I've seen the same behavior. For some reason
>>> PYTHON_EXECUTABLE:FILEPATH
>>> points to the python2 executable instead of python3.
>>> A workaround is to change it to point to the correct python and that
>>> fixes the problem.
>>> I have not looked into why the variable is set this way.
>>>
>>> Dan
>>>
>>>
>>>>
>>
>> --
>> ___________________________________________
>> Andrew J. P. Maclean
>>
>> ___________________________________________
>>
>
>
> --
> ___________________________________________
> Andrew J. P. Maclean
>
> ___________________________________________
>


-- 
___________________________________________
Andrew J. P. Maclean

___________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://vtk.org/pipermail/vtk-developers/attachments/20190113/eeff3dac/attachment-0001.html>