[vtkusers] kwsys in custom source

[Patrick D. Emond]

That did the trick, thanks Brad.

I have one other related question that I'm not sure whether you can help 
with (or anyone else on the list, for that matter).  Now that we're 
using this SystemInformation library by adding in the appropriate lines 
to the LocalUserOptions.cmake file in our VTK build tree, is there some 
way check in our application's CMake configuration whether or not the 
VTK library being used has the SystemInformation library built in?

In case my question isn't clear, I would like a way to test at the cmake 
configure stage of my application whether or not the SystemInformation 
stuff has been built into VTK so that if in the future we rebuild VTK 
and forget to add in the LocalUserOptions.cmake file we'll get an error 
during configuration instead of during the link stage.


Brad King wrote:
> Patrick D. Emond wrote:
>> I make installed VTK as a shared build (and confirmed that vtksys.dll 
>> was found in the install bin directory).  From here I've built an 
>> application that uses the SystemInformation code and I get the 
>> following linker errors:
> 
> The SystemInformation tool was only recently added.  It looks like this 
> is the first time someone is trying to use it built shared on Windows. 
> The class does not have the proper export macro.
> 
> In SystemInformation.hxx.in, change the line
> 
>   class SystemInformation
> 
> to
> 
>   class @KWSYS_NAMESPACE at _EXPORT SystemInformation
> 
> and run CMake again to configure it.
> 
> If that works I'll commit the change in KWSys.
> 
> -Brad
>