[vtkusers] cvs update / cmake build problems fails the 2nd time
Dominik Szczerba
domi at vision.ee.ethz.ch
Mon Jun 18 08:16:51 EDT 2007
Hi Amy,
What I meant was: I failed to build the project AFTER 'cvs ... update'.
THEN I removed (actually, renamed to VTK.old) the source tree, and did
'cvs .... checkout' into a clean VTK/ folder. This one built fine. My
question was: why did the updated version fail to build and the checked
out version not.
- Dominik
Amy Squillacote wrote:
> Hi Dominik,
>
> You mentioned in your original email that you removed the source
> directory. If you removed the top level of the source tree (something
> like rm -r VTK/), then you won't have anything left to do a cvs update
> from (even with the -d option). If you completely remove the source
> directory, you'll have to do cvs checkout. This is a matter of how cvs
> operates; it is not VTK-specific.
>
> - Amy
>
> Dominik Szczerba wrote:
>> I have only a passive knowledge of CVS. I didn't use/know -d. Thanks
>> for the hint, will try next time.
>> - Dominik
>>
>> Bryn Lloyd wrote:
>>> Hi Dominik,
>>>
>>> Did you write "cvs update", or "cvs update -d"?
>>>
>>> If the "-d" option is not used new files will be added, but new
>>> directories not. Each directory in the Wrapping/Python tree has a
>>> __init_.py file. Maybe it was not found because, the directory was
>>> not added ...
>>>
>>> Hope I could help.
>>>
>>> Cheers
>>> Bryn
>>>
>>>
>>>
>>> Dominik Szczerba wrote:
>>>> Thanks for the hint about the dashboard. Note however, that a clear
>>>> checkout succeeded to build, it was the update that failed. So my
>>>> point is either I am using CVS in a wrong way (simply update instead
>>>> of checkout?) or the cvs tree is not consistent (?)
>>>> - Dominik
>>>>
>>>> Andrew Maclean wrote:
>>>>> You must check the state of the dashboard before doing an update.
>>>>> There is no guarantee that all the code is stable in the CVS. It is
>>>>> development code.
>>>>>
>>>>> Andrew
>>>>>
>>>>>
>>>>>
>>>>> On 6/17/07, *Dominik Szczerba* <domi at vision.ee.ethz.ch
>>>>> <mailto:domi at vision.ee.ethz.ch>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> Second time I encountered problems while rebuilding VTK after
>>>>> updating
>>>>> from CVS. Last time I dont remember what the error was, this
>>>>> time it
>>>>> failed on python bindings (missing __init.py somewhare at the
>>>>> very very
>>>>> end). Removing both the source and build directories, checking
>>>>> out a
>>>>> clean tree and building from scratch fixed both problems. But
>>>>> is VTK
>>>>> not
>>>>> meant to be updated via 'cvs ... update'? Did I miss anything?
>>>>> Regards,
>>>>> Dominik
>>>>> --
>>>>> Dominik Szczerba, Ph.D.
>>>>> Computer Vision Lab CH-8092 Zurich
>>>>> http://www.vision.ee.ethz.ch/~domi
>>>>> <http://www.vision.ee.ethz.ch/~domi>
>>>>> _______________________________________________
>>>>> This is the private VTK discussion list.
>>>>> Please keep messages on-topic. Check the FAQ at:
>>>>> http://www.vtk.org/Wiki/VTK_FAQ <http://www.vtk.org/Wiki/VTK_FAQ>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://www.vtk.org/mailman/listinfo/vtkusers
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> ___________________________________________
>>>>> Andrew J. P. Maclean
>>>>> Centre for Autonomous Systems
>>>>> The Rose Street Building J04
>>>>> The University of Sydney 2006 NSW
>>>>> AUSTRALIA
>>>>> Ph: +61 2 9351 3283
>>>>> Fax: +61 2 9351 7474
>>>>> URL: http://www.cas.edu.au/
>>>>> ___________________________________________
>>>>
>>>>
>>
>>
>
--
Dominik Szczerba, Ph.D.
Computer Vision Lab CH-8092 Zurich
http://www.vision.ee.ethz.ch/~domi
More information about the vtkusers
mailing list