[vtk-developers] VTK Wrapping

David Gobbi david.gobbi at gmail.com
Fri Jul 2 16:49:50 EDT 2010


That's good news.  If you touch just one header file, will that cause
all the wrappers to recompile?

Of course it shouldn't, and I'm 90% sure that the dependencies are set
up properly for makefiles (I looked through the generated makefiles a
couple days ago).  Whether devenv is doing the right thing, I'm not so
sure.  One of the Windows dashboard machines seems to be having
issues.

  David


On Fri, Jul 2, 2010 at 2:38 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> David,
>
> I just did a pull followed by a make.
> Then another make.
> The second make did not rebuild anything.
> Fedora Core 13, gcc 4.4.4
> Cmake 2.8.2-rc2
> VTK_WRAP_TCL:BOOL=ON
> As I expected.
>
> Then did
> cmake ../VTK
> make
> Nothing was rebuilt.
> As I expected.
>
> Bill
>
> On Fri, Jul 2, 2010 at 3:38 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>> Just another note about the wrapping, it was pushed this morning and
>> the dashboard hasn't suffered too badly.  Most of the issues are
>> minor, except for a troublesome dependency that I'll add a quick-fix
>> patch for if I cannot fix it properly today.
>>
>> I would just like to say that these changes are meant to be backwards
>> compatible with existing code that uses the wrappers.  So if you see
>> something break, don't try to fix your code, email your issue to the
>> developers list so that I can fix it.
>>
>> If people do not email the list or enter a bug when the new wrappers
>> break something, then I will not be able to fix the wrappers to keep
>> them backwards compatible.  And if I do not keep them backwards
>> compatible, then over the long term a lot of people will suffer.  So
>> in summary, if these changes break your code, and you do not email the
>> list, then you are evil.
>>
>> And we all want to be good, right?
>>
>>   David
>>
>>
>> On Tue, Jun 29, 2010 at 9:34 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>>> An update: I will be pushing the next batch of Wrapping updates on
>>> Friday morning.  These changes will only involve the Wrapping
>>> directory and some additions to CMake. I will push the necessary
>>> changes to ParaView's ClientServer wrapper at the same time.
>>>
>>> This update is much smaller in scope than the previous one, so I'll
>>> just test it on my own Mac/Linux/PC and then let the Dashboard have at
>>> it, unless there are serious objections.  Over the weekend I'll be
>>> watching the dashboard.
>>>
>>>  David
>>>
>>>
>>>
>>> On Mon, Jun 21, 2010 at 5:40 AM, David Gobbi <david.gobbi at gmail.com> wrote:
>>>> Just a quick heads up,
>>>>
>>>> I have some more code to merge into the Wrapping subdirectory, so if
>>>> anyone plans to make any changes there, please wait a couple weeks
>>>> until I get everything finished.  Here are the items that I still have
>>>> to merge:
>>>>
>>>> 1) My "vtkWrapHierarchy.c" for proper type-checking in the wrappers,
>>>> see http://www.vtk.org/Wiki/VTK/WrapHierarchy .  This is an essential
>>>> part of the wrapper changes, but one that I didn't have ready for the
>>>> initial merge.
>>>>
>>>> 2) A new file "vtkParseMain.c" that will contain the "main()" for the
>>>> wrappers, so that "main()" is no longer part of vtkParse.y.  This
>>>> change will allow wrapper-generators to read multiple header files,
>>>> and to use "-I" command-line arguments for the include path.  Needed
>>>> for vtkWrapHierarchy.
>>>>
>>>> 3) A modified "vtkParse.h" that stores information about any helper
>>>> classes that it finds in the header files, i.e. the FileInfo struct
>>>> can have multiple ClassInfo structs.  Also needed for
>>>> vtkWrapHierarchy.
>>>>
>>>> These three items will require some changes to
>>>> vtkWrapPython/Tcl/Java/ClientServer that I haven't started on yet
>>>> (fairly small changes, thankfully).
>>>>
>>>>   David
>>>>
>>>
>> _______________________________________________
>> 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
>>
>>
>



More information about the vtk-developers mailing list