Hello Luca,

 I checked and my SuperBuild.cmake says on lines 45 and 46:
    GIT_REPOSITORY "${GIT_PROTOCOL}://github.com/Kitware/ITK.git"
    GIT_TAG "v3.20.1"
which is different from the superbuild cmake file you mentioned. In fact I 
realized there was something strange going on last night. I had the problem 
with itk compilation on a desktop machine, but not in my laptop (which I 
updated after the desktop). Git pull in the desktop machine doesn't update the 
SuperBuild.cmake or anything else, so I looked at the output of git remote -v 
and I have this (in my desktop):
origin  git://vmtk.git.sourceforge.net/gitroot/vmtk/vmtk (fetch)
origin  git://vmtk.git.sourceforge.net/gitroot/vmtk/vmtk (push)

Vmtk is now on github so I cloned the new repo from there and the new  
SuperBuild.cmake which it contains is identical to the one you refer to.

To summarize: it's my fault, I've been using an old repository which I cloned 
a long time ago. Sorry about the confusion.

Best regards,

   Martin Vymazal


On Tuesday 18 September 2012 11:37:06 Luca Antiga wrote:

Dear Martin,
 thank you for your report, it's indeed a ITK issue.


It is weird that it is happening now, though, since I forked ITK and created 
a 
3.20.1-vmtk branch in which the issue was solved exactly as you describe:
https://github.com/vmtk/ITK/commit/0f47d151788280e3bca3c5e50968117584b71296


Superbuild should get it that branch:
https://github.com/vmtk/vmtk/blob/master/SuperBuild.cmake, lines 36, 37 


The current port (in progress for a while now - but coming soon... ouch!) to 
ITK4 should 
solve the issue at the root, but I wonder why you still got the issue.


Can you check if your SuperBuild.cmake file at lines 36 and 37 and see if it's 
the
same as the one linked above?


Thanks and best regards


Luca




On Sep 17, 2012, at 4:44 PM, Martin Vymazal wrote:

Dear vmtk users,

I'm sending this email just in case someone has a similar problem as 
described below. I encountered two slight hiccups when compiling vmtk from 
superbuild:

1)  vmtk-build/ITK/Code/Algorithms/itkCurvesLevelSetFunction.h:102:55: error: 
‘PropagationSpeed’ was not declared in this scope, and no declarations were 
found by argument-dependent lookup at the point of instantiation

This can be fixed by changing line 102 in itkCurvesLevelSetFunction.h from:
  { return PropagationSpeed( neighborhood, offset, gd ); }
to
 { return this->PropagationSpeed( neighborhood, offset, gd ); }


2) A similar error occurs in vmtk-
build/ITK/Code/Algorithms/itkGeodesicActiveContourLevelSetFunction.h

Change line 117 from:
   return PropagationSpeed( neighborhood, offset, gd );
to
   return this->PropagationSpeed( neighborhood, offset, gd );


After that, everything compiled fine. I use Arch linux with gcc 4.7.1. The 
only non-default setting in the superbuild was build type - I used 
RelWithDebInfo.

Best regards,

 Martin Vymazal

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
vmtk-users mailing list
vmtk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vmtk-users





------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
vmtk-users mailing list
vmtk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vmtk-users

Reply via email to