On 19. May, 2009, at 17:58, e...@cs.bgu.ac.il wrote:
I'm writing a program which is based on 3 external libs, Poco,
ARToolKit and opencv, now the locations in the include folder is has
followd:
opencv headers are in /usr/include/opencv folder, Poco headers are
in /usr/include/Poco folder
On Tue 19 May 3:29 2009 Christopher Harvey wrote:
> I'm not sure how to explain the fact that arMulti.h is reported as
> located in /usr/includeI'm not sure but maybe you have to delete the
> CMakeCache file...I don't think cmake has any bugs like finding files
> that don't exist. Your script
I'm not sure how to explain the fact that arMulti.h is reported as
located in /usr/includeI'm not sure but maybe you have to delete the
CMakeCache file...I don't think cmake has any bugs like finding files
that don't exist. Your script seems fine from what I see. Maybe you can
post a bit more?
I don't know how the ARTK library is installed on linux systems, but you
could add the NO_DEFAULT_PATH option to find_path...chances are it's
looking in a default path and picking up a header in /usr/include before
getting to your specified directories. What makes you think the
/usr/include is bad?
I'm writing a program which is based on 3 external libs, Poco, ARToolKit and
opencv, now the locations in the include folder is has followd:
opencv headers are in /usr/include/opencv folder, Poco headers are in
/usr/include/Poco folder and ARToolKit headers are in /usr/include/AR folder.
I'm try
