KDL build errors on Windows
Submitted by dustingooding on Thu, 2011-06-23 06:00 |
Windows XP, Visual Studio 10. I checked out the latest KDL from SVN. I used CMake to point to Eigen2.
When I build the ALL_BUILD project, I get the following errors:
/**
1>------ Build started: Project: orocos-kdl, Configuration: Debug Win32 ------
1> chaindynparam.cpp
1> chainiksolvervel_pinv_nso.cpp
1> Generating Code...
1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(132): error C4716: 'KDL::ChainIkSolverVel_pinv_nso::setWeights' : must return a value
1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(136): error C4716: 'KDL::ChainIkSolverVel_pinv_nso::setOptPos' : must return a value
1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(140): error C4716: 'KDL::ChainIkSolverVel_pinv_nso::setAlpha' : must return a value
1>c:\orocos-kdl-svn\src\chaindynparam.cpp(105): warning C4715: 'KDL::ChainDynParam::JntToMass' : not all control paths return a value
1>c:\orocos-kdl-svn\src\chaindynparam.cpp(118): error C4716: 'KDL::ChainDynParam::JntToCoriolis' : must return a value
1>c:\orocos-kdl-svn\src\chaindynparam.cpp(129): error C4716: 'KDL::ChainDynParam::JntToGravity' : must return a value
========== Build: 0 succeeded, 1 failed, 2 up-to-date, 0 skipped ==========
**/
Sure enough, those functions expect to return an int and have no return statements. I guess it's OK to add "return 0;" to the end of all of them?
--
Dustin Gooding
KDL build errors on Windows
On Thu, Jun 23, 2011 at 7:39 AM, Gooding, Dustin R. (JSC-ER411)
<dustin [dot] r [dot] gooding [..] ...> wrote:
> Windows XP, Visual Studio 10. I checked out the latest KDL from SVN. I
> used CMake to point to Eigen2.
> When I build the ALL_BUILD project, I get the following errors:
> /**
> 1>------ Build started: Project: orocos-kdl, Configuration: Debug Win32
> ------
> 1> chaindynparam.cpp
> 1> chainiksolvervel_pinv_nso.cpp
> 1> Generating Code...
> 1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(132): error C4716:
> 'KDL::ChainIkSolverVel_pinv_nso::setWeights' : must return a value
> 1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(136): error C4716:
> 'KDL::ChainIkSolverVel_pinv_nso::setOptPos' : must return a value
> 1>c:\orocos-kdl-svn\src\chainiksolvervel_pinv_nso.cpp(140): error C4716:
> 'KDL::ChainIkSolverVel_pinv_nso::setAlpha' : must return a value
> 1>c:\orocos-kdl-svn\src\chaindynparam.cpp(105): warning C4715:
> 'KDL::ChainDynParam::JntToMass' : not all control paths return a value
> 1>c:\orocos-kdl-svn\src\chaindynparam.cpp(118): error C4716:
> 'KDL::ChainDynParam::JntToCoriolis' : must return a value
> 1>c:\orocos-kdl-svn\src\chaindynparam.cpp(129): error C4716:
> 'KDL::ChainDynParam::JntToGravity' : must return a value
> ========== Build: 0 succeeded, 1 failed, 2 up-to-date, 0 skipped ==========
> **/
> Sure enough, those functions expect to return an int and have no return
> statements. I guess it's OK to add "return 0;" to the end of all of them?
I think so. The KDL maintainer is in holidays... maybe you could
submit it as a bug report here: http://bugs.orocos.org
such that it isn't overlooked.
Peter
--
Orocos-Users mailing list
Orocos-Users [..] ...
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users