<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/28/18 11:00 AM, Ben Boeckel
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20181128160041.GA25730@megas.kitware.com">
<pre class="moz-quote-pre" wrap="">On Tue, Nov 27, 2018 at 19:02:14 -0500, Jean-Christophe Fillion-Robin wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Should I just ignore the libvtkPythonInterpreter and leave the
PYTHON_LIBRARY field blank?
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">
It being blank will cause `find_library` to try and find it itself. I
think the error is that now an empty linker script is not valid, but I'm
not sure. Is it possible to use an older compiler/linker to make the
wheels?</pre>
</blockquote>
<p>Unfortunately, that is a pain, so no, I don't think it would be
convenient or meaningful to expect an older compiler/linker.<br>
</p>
<p>
</p>
<blockquote type="cite"
cite="mid:20181128160041.GA25730@megas.kitware.com">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">It looks like introducing an option to conditionally build
vtkPythonInterpreter would address the issue here.
@Ben: What do you think ?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
How would this work? If it is disabled, `vtkWrappingPythonCore` (a
dependency of all wrapped Python modules) and `vtkRenderingMatplotlib`
can't be built.</pre>
</blockquote>
<p>Does vtkWrappingPythonCore depend on vtkPythonInterpreter?
vtkWrappingPythonCore does not link to libpython or to
vtkPythonInterpreter. The wheels by default do not seem to enable
vtkRenderingMatplotlib although I am not sure if it should be
added by default in the future, in which case this is a more
serious issue.<br>
</p>
<blockquote type="cite"
cite="mid:20181128160041.GA25730@megas.kitware.com">
<pre class="moz-quote-pre" wrap="">
For the record, the new module system's way of doing this is here:
<a class="moz-txt-link-freetext" href="https://gitlab.kitware.com/ben.boeckel/vtk/blob/new-cmake-module/Utilities/Python/CMakeLists.txt#L118">https://gitlab.kitware.com/ben.boeckel/vtk/blob/new-cmake-module/Utilities/Python/CMakeLists.txt#L118</a>
Basically, the `VTK::Python` module contains the library for
executables, but is just the magic flags to ignore the missing symbols
when linking libraries. So, it should "just work", but it does require
3.13+ for `target_link_options` (without it, direct linking is used). It
can't really be backported because the old module system is quite
allergic to CMake's target stuff (since it was designed basically as the
same thing, but predate's CMake's logic).</pre>
</blockquote>
<p>I think requiring a newer CMake is fairly reasonable if that will
solve the problem unless I am missing something obvious here
(which is very likely).</p>
<p>cheers,</p>
<p>Prabhu<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:20181128160041.GA25730@megas.kitware.com">
<pre class="moz-quote-pre" wrap="">
--Ben
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>