[vtkusers] ANNOUNCE: vtk 6.0.0.rc1 is available to download

[Marcus D. Hanwell]

Thanks for reporting back, I was wondering if it was more an issue of
an inconsistent build tree. I would strongly encourage the use of
COMPONENTS in your find VTK calls so that you don't end up linking to
all of the compiled VTK modules (the default when no components are
specified).

Thanks,

Marcus

On Fri, May 24, 2013 at 10:56 AM, Dženan Zukić <dzenanz at gmail.com> wrote:
> I cleanly redid the configuration and compilation steps (of both RC1 and git
> master), and I don't get the problem any more.
>
>
> On Thu, May 23, 2013 at 10:09 PM, Bill Lorensen <bill.lorensen at gmail.com>
> wrote:
>>
>> Dzenan,
>>
>> Here is a patch to address your issues:
>> http://review.source.kitware.com/#/c/11394/
>>
>> Please register for a gerrit account so you can contribute in the future.
>>
>> Thanks for your efforts to towards a better VTK.
>>
>> Bill
>>
>>
>>
>> On Thu, May 23, 2013 at 3:51 PM, Dženan Zukić <dzenanz at gmail.com> wrote:
>>>
>>> Yes, I am using RC1 from the download page
>>> (http://www.vtk.org/files/release/6.0/vtk-6.0.0.rc1.zip).
>>>
>>> I will intersperse a few message() calls in CMakeLists.txt tomorrow and
>>> report the results. It is 9:51 pm here in Germany :D
>>>
>>>
>>> On Thu, May 23, 2013 at 9:34 PM, Marcus D. Hanwell
>>> <marcus.hanwell at kitware.com> wrote:
>>>>
>>>> Adding message(FATAL_ERROR "VTK_LIBRARIES: ${VTK_LIBRARIES}") to your
>>>> CMakeLists.txt would be helpful. That variable is populated each time
>>>> you call find_package(VTK COMPONENTS vtkModuleName NO_MODULE) with the
>>>> module you ask for and all of its dependencies. If it is called
>>>> without a COMPONENTS argument it defaults to containing all enabled
>>>> modules - that looks like the case here with the config file perhaps
>>>> being out of sync with the build for some reason.
>>>>
>>>> I can't reproduce your failure here, but will take a second look on
>>>> Windows. Can you confirm you are building against VTK 6.0.0 RC1? It is
>>>> possible you have some config files hanging around for the modules
>>>> that were later disabled - I can try this on Windows later to see if
>>>> it is an issue. Is you VTK_DIR referencing the build tree, or an
>>>> installed VTK 6.0 in this case?
>>>>
>>>> Marcus
>>>>
>>>> On Thu, May 23, 2013 at 3:24 PM, Dženan Zukić <dzenanz at gmail.com> wrote:
>>>> > Attached is the version of my CMakeLists.txt before I started meddling
>>>> > with
>>>> > find_package(vtk). It makes not difference to change it to this:
>>>> > FIND_PACKAGE(VTK 6.0 REQUIRED COMPONENTS vtkGUISupportQtOpenGL
>>>> > NO_MODULE)
>>>> >
>>>> > Also, it is these 3 libraries which are included into projects input
>>>> > erroneously:
>>>> > vtkTestingGenericBridge.lib
>>>> > vtkTestingIOSQL.lib
>>>> > vtkTestingRendering.lib
>>>> >
>>>> >
>>>> > On Thu, May 23, 2013 at 9:07 PM, Marcus D. Hanwell
>>>> > <marcus.hanwell at kitware.com> wrote:
>>>> >>
>>>> >> On Thu, May 23, 2013 at 11:19 AM, Marcus D. Hanwell
>>>> >> <marcus.hanwell at kitware.com> wrote:
>>>> >> > On Thu, May 23, 2013 at 11:13 AM, Dženan Zukić <dzenanz at gmail.com>
>>>> >> > wrote:
>>>> >> >> Now I call vtk from CMakeLists like this:
>>>> >> >> FIND_PACKAGE(VTK 6.0 REQUIRED COMPONENTS vtkGUISupportQtOpenGL
>>>> >> >> NO_MODULE)
>>>> >> >>
>>>> >> >> but when compiling the project I still get LNK1181 with
>>>> >> >> vtkTestingGenericBridge.lib if I keep BUILD_TESTING set to off.
>>>> >> >>
>>>> >> >> Setting BUILD_TESTING to 1 solves the issue (regardless of the way
>>>> >> >> how
>>>> >> >> find_package is called). But I think it is stupid to require users
>>>> >> >> to
>>>> >> >> enable
>>>> >> >> building of internal tests just so their normal applications can
>>>> >> >> link
>>>> >> >> properly.
>>>> >> >>
>>>> >> > No one is suggesting you should have to turn on testing for your
>>>> >> > normal application to work. It looks like you have found a bug, and
>>>> >> > we
>>>> >> > will work on ensuring it is fixed in the next rc. Thanks for
>>>> >> > testing,
>>>> >> > and your feedback.
>>>> >> >
>>>> >> On looking into this further I am unable to reproduce it. I see you
>>>> >> are doing this on Windows, and vtkTestingGenericBridge seems to be
>>>> >> giving you the issue. This is only referenced by the
>>>> >> vtkFiltersGeneric
>>>> >> TEST_DEPENDS as far as I can tell, could you provide a fuller sample
>>>> >> of your CMake code? It looks like you are trying to find
>>>> >> vtkGUISupportQtOpenGL, which has no dependency on this module,
>>>> >> printing the contents of ${VTK_LIBRARIES} would be useful, along with
>>>> >> exact VTK version (RC1 I guess), compiler, steps to build VTK
>>>> >> locally.
>>>> >>
>>>> >> Thanks for reporting this issue, hopefully we can get to the bottom
>>>> >> of
>>>> >> this soon (I can give this a try on a Windows machine, but I don't
>>>> >> see
>>>> >> how vtkTestingGenericBridge is getting linked to from
>>>> >> vtkGUISupportQtOpenGL to be honest - even with testing turned on).
>>>> >>
>>>> >> Marcus
>>>> >
>>>> >
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the VTK FAQ at:
>>> http://www.vtk.org/Wiki/VTK_FAQ
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.vtk.org/mailman/listinfo/vtkusers
>>>
>>
>>
>>
>> --
>> Unpaid intern in BillsBasement at noware dot com
>
>