You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Fresh checkout, cmake and build (maybe just on linux..)
What is the expected output? What do you see instead?
Should build fine. Instead:
/home/steve/OpenCV/gsoc2011sfm/YAML_loader/main.cpp|144|error: no matching
function for call to
‘transform(
__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
__gnu_cxx::__normal_iterator<char*, std::basic_string<char,
std::char_traits<char>, std::allocator<char> > >,
<unresolved overloaded function type>)’|
Please use labels and text to provide additional information.
After switching to eigen-3.0.1 like you suggested it compiled and ran fine
(although a couple of tests still weren't working). I then tried a clean
checkout and build and suddenly I am getting this error when I try to
compile... :/
Maybe it has something to do with this warning in CMake:
CMake Warning at ProjectAdd.cmake:87 (add_executable):
Cannot generate a safe linker search path for target SfM_YAML_loader
because files in some directories may conflict with libraries in implicit
directories:
link library [libpng.so] in /usr/lib may be hidden by files in:
/usr/local/share/opencv/../../lib
/usr/local/lib
Some of these libraries may not be found correctly.
Call Stack (most recent call first):
YAML_loader/CMakeLists.txt:2 (new_executable)
Original issue reported on code.google.com by stephen....@gmail.com on 5 Sep 2011 at 12:34
The text was updated successfully, but these errors were encountered:
Fixed in the last commit...
The warning is due to the libpng created by opencv and libmv which have the
same name in two different path. Cmake doesn't know which one to use...
But this doesn't seems problematic, I hope for you either...
Original comment by thibault...@gmail.com on 5 Sep 2011 at 10:12
Original issue reported on code.google.com by
stephen....@gmail.com
on 5 Sep 2011 at 12:34The text was updated successfully, but these errors were encountered: