[vtk-developers] Is there any documentation for VTK wrapping?

[Darren Weber]

I'm working on the package for vtk 5-4-0 in macports (vtk-devel).  The
src/Wrapping/README.txt indicates a dependency on yacc (byacc) and flex.  I
have the following available (through macports), which dependency should I
use?

*****************************************************************************

bison @2.4.1 (devel)
    general-purpose parser generator

bison1 @1.875 (devel, lang)
    general-purpose parser generator

byacc @20090221 (devel)
    Berkeley Yacc

flex @2.5.35 (devel)
    Fast lexical analyser generator

py-bison @0.1.8 (python, lang)
    Python-based parsing at the speed of C

*****************************************************************************

bison @2.4.1 (devel)
Variants:    universal, yacc

Bison is a general-purpose parser generator that converts a grammar
description for an LALR context-free grammar into a C program to
parse that grammar. Once you are proficient with Bison, you can use it to
develop a wide range of language parsers, from those used in
simple desk calculators to complex programming languages.
Homepage:    http://www.gnu.org/software/bison/

Library Dependencies: gettext, m4, libiconv
Platforms:            darwin
Maintainers:          mww at macports.org

*****************************************************************************

byacc @20090221 (devel)
Variants:    universal

Berkeley Yacc (byacc) is generally conceded to be the best yacc variant
available. In contrast to bison, it is written to avoid
dependencies upon a particular compiler.
Homepage:    http://invisible-island.net/byacc/

Platforms:            darwin
Maintainers:          toby at macports.org

*****************************************************************************


Furthermore, if both bison yacc and byacc are installed, how are they
called; ie, how do we control which one is used?

Thanks in advance,
Darren





On Mon, May 4, 2009 at 1:17 PM, David Thompson <dcthomp at sandia.gov> wrote:

> > Does the python (and other lang) wrapping depend on swig?
> No, the wrapping in VTK is a parser written in C with the help of lex
> and yacc. It was written before SWIG existed, as I recall.
>
>        David
>
> > On Mon, May 4, 2009 at 11:27 AM, pat marion <pat.marion at kitware.com>
> > wrote:
> >         Another helpful detail- you can tell the wrapper to ignore
> >         certain
> >         files by using this in your CMakeLists.txt:
> >
> >         SET_SOURCE_FILES_PROPERTIES(
> >          vtkMyUnwrappableClass.cxx
> >          WRAP_EXCLUDE
> >         )
> >
> >         Pat
> >
> >
> >         On Mon, May 4, 2009 at 1:22 PM, David E DeMarle
> >         <dave.demarle at kitware.com> wrote:
> >         > A search on markmail turned up a fairly recent discussion of
> >         the topic.
> >         >
> >         > http://vtk.markmail.org/search/?q=wrapping#query:wrapping
> >         +page:1+mid:plwydwprhlreh24s+state:results
> >         >
> >         > It doesn't look the the wiki page was ever moved over to
> >         vtk.org. I
> >         > will do that now.
> >         >
> >         > David E DeMarle
> >         > Kitware, Inc.
> >         > R&D Engineer
> >         > 28 Corporate Drive
> >         > Clifton Park, NY 12065-8662
> >         > Phone: 518-371-3971 x109
> >         >
> >         >
> >         >
> >         > On Mon, May 4, 2009 at 1:12 PM, kent williams
> >         <nkwmailinglists at gmail.com> wrote:
> >         >> Maybe I'm just missing the tree I need for the forest, but
> >         I went
> >         >> looking for documentation on VTK Wrapping, and came up
> >         empty.
> >         >>
> >         >> In fact, in the top ten hits for google search on "vtk
> >         wrapping"  my
> >         >> own posts to the VTK-Users come up, the ones where I claim
> >         that VTK
> >         >> wrapping are driving me insane.
> >         >>
> >         >> I've acquired the bare minimum knowledge necessary to
> >         survive VTK
> >         >> wrapping for KWWidgets applications --- use //BTX and //ETX
> >         to keep
> >         >> the wrapping parser from losing its mind, always name
> >         classes with a
> >         >> 'vtk' prefix, limit argument types to built-in scalar types
> >         and char *
> >         >> -- but is VTK wrapping actually documented anywhere?
> >         >> _______________________________________________
> >         >> Powered by www.kitware.com
> >         >>
> >         >> Visit other Kitware open-source projects at
> >         http://www.kitware.com/opensource/opensource.html
> >         >>
> >         >> Follow this link to subscribe/unsubscribe:
> >         >> http://www.vtk.org/mailman/listinfo/vtk-developers
> >         >>
> >         >>
> >         > _______________________________________________
> >         > Powered by www.kitware.com
> >         >
> >         > Visit other Kitware open-source projects at
> >         http://www.kitware.com/opensource/opensource.html
> >         >
> >         > Follow this link to subscribe/unsubscribe:
> >         > http://www.vtk.org/mailman/listinfo/vtk-developers
> >         >
> >         >
> >         _______________________________________________
> >         Powered by www.kitware.com
> >
> >         Visit other Kitware open-source projects at
> >         http://www.kitware.com/opensource/opensource.html
> >
> >         Follow this link to subscribe/unsubscribe:
> >         http://www.vtk.org/mailman/listinfo/vtk-developers
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20090504/2a1fac0c/attachment.html>