[vtkusers] is a machine readable list of classes and methods available?

[JTK]

Thank you!  This looks like what I need.

I tried it, and it chokes on missing 

-- Detecting CXX compile features - done
CMake Error at CMake/vtkIncludeAllKits.cmake:22 (include):
  include could not find load file:

    /opt/local/lib/cmake/vtk-7.0/Modules/vtkChartsCore-Headers.cmake
Call Stack (most recent call first):
  CMakeLists.txt:54 (INCLUDE)


I assume this means that some installations of vtk aren’t sufficient (I’m using the canned macports install)?

Is there a name for the feature that installs the xxx-Headers.cmake files?

J.Klein




> On Oct 4, 2016, at 5:27 PM, David Gobbi <david.gobbi at gmail.com> wrote:
> 
> Hi J,
> 
> My WrapVTK project uses the VTK wrapper machinery to create an XML file for each of the VTK classes, the process only takes a couple minutes.  It can be found here:
> 
> http://github.com/dgobbi/WrapVTK <https://github.com/dgobbi/WrapVTK>
> 
>  - David
> 
> 
> 
> On Tue, Oct 4, 2016 at 8:35 PM, JTK <jetmonk at gmail.com <mailto:jetmonk at gmail.com>> wrote:
> 
> Hello,
> 
> I’m trying to make VTK usable from the common lisp language using the Common Lisp CFFI [1] package, translating C++ methods/classes into CLOS methods/classes.
> 
> I understand that VTK supports internal automated ways of doing this (used for Python and TCL glue code generation), but these are a bit excessive for my purposes (and specialized).  Other methods like SWIG seem to choke on VTK code - maybe it’s all the macros? Instead, I’ve written a general package for wrapping C++ methods and classes into Lisp to let me hand-wrap VTK classes.
> 
> Is there a machine readable list of the C++ class/method hierarchy available?
> 
> Something like:
> 
> {class: “vtkCylinderSource”
>  parents: {“vtkPolyDataAlgorithm”}
>  methods: {{method: SetHeight 
>             returntype: void
>             arguments: {{“height” “double”}}}
>            }
> }
> 
> 
> Or an equivalent in XML.  Or maybe simplified macro-less C++ definitions that I could parse?
> 
> Such a list of methods seems to exist implicitly for the documentation, but it isn’t machine readable. Is there a machine readable one, or is there an easy way to make it?
> 
> Thanks for any tips,
> J.Klein
> 
> 
> 
> [1] cffi: https://common-lisp.net/project/cffi/ <https://common-lisp.net/project/cffi/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20161004/77310d20/attachment.html>