I previously stated that there were 4 "Cannot open include file" errors.
Turns out there are just 3. I've listed them all below.
On all of my dashboard builds I set this
SET (CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)
in the Ctest script. So I would expect this error on the dashboard.
Strange.
One potential solution is to configure contrib\gel\mrc\vpgl\algo after
brl. There are some other similar exceptions like this that you'll see
at the bottom contrib/CMakeLists.txt. Ugly, but it works. How about
I'll put in a "fix" like that in a couple of days if there is no
objection in the meantime?
Fred
[ 90%] Building CXX object
contrib/gel/mrc/vpgl/algo/CMakeFiles/vpgl_algo.dir/vpgl_camera_compute.o
bj
vpgl_camera_compute.cxx
D:\home\wheeler\dev\vxl_src\contrib\gel\mrc\vpgl\algo\vpgl_camera_comput
e.cxx(25) : fatal error C1083: Cannot open include file:
'bgeo/bgeo_lvcs.h': No such file or directory
[ 90%] Building CXX object
contrib/gel/mrc/vpgl/algo/CMakeFiles/vpgl_algo.dir/vpgl_bundle_adjust.ob
j
vpgl_bundle_adjust.cxx
d:\home\wheeler\dev\vxl_src\contrib\gel\mrc\vpgl\algo\vpgl_bundle_adjust
.h(10) : fatal error C1083: Cannot open include file:
'bnl/bnl_sparse_lst_sqr_function.h': No such file or directory
[ 91%] Building CXX object
contrib/gel/mrc/vpgl/algo/tests/CMakeFiles/vpgl_algo_test_all.dir/test_b
undle_adjust.obj
test_bundle_adjust.cxx
D:\home\wheeler\dev\vxl_src\contrib\gel\mrc\vpgl/algo/vpgl_bundle_adjust
.h(10) : fatal error C1083: Cannot open include file:
'bnl/bnl_sparse_lst_sqr_function.h': No such file or directory
=20
-----Original Message-----
From: vxl-maintainers-bounces@...
[mailto:vxl-maintainers-bounces@...] On Behalf Of Matt
Leotta
Sent: Monday, November 19, 2007 2:34 PM
To: Joseph Mundy; vxl-maintainers
Cc: Gamze Tunali; Thom Pollard
Subject: Re: [Vxl-maintainers] FW: BRL_INCLUDE_DIR
I think the culprit is actually vpgl_algo not vpgl. It looks like
vpgl_algo is linked to bnl_algo and bgeo. I know that bnl_algo is used
for my sparse levenberg marquardt implementation for bundle adjustment.
The sparse LM code is very general and should not moved into vpgl. If
anything it should be moved into vnl_algo. I can make that move if
there are no objections.
The actual error Fred is receiving comes from bgeo, which I don't know
anything about. Thom or Gamze would have to make the call on whether or
not it is appropriate to move that.
--Matt
On Nov 19, 2007 2:02 PM, Joseph Mundy <mundy@...> wrote:
> Matt, Thom,
> Is there something you use from brl in your vpgl stuff?
> If so maybe it can be moved to vpgl.
> Prof. Mundy
> -----Original Message-----
> From: vxl-maintainers-bounces@...
> [mailto:vxl-maintainers-bounces@...] On Behalf Of=20
> Amitha Perera
> Sent: Monday, November 19, 2007 11:32 AM
> To: Wheeler, Frederick W (GE, Research)
> Cc: vxl-maintainers@...
> Subject: Re: [Vxl-maintainers] BRL_INCLUDE_DIR
>
> I think you are correct about the build order affecting things. My=20
> guess is that most dashboard builds don't start from scratch each
night.
>
> Brown folks: could you guys look into resolving this? Should vpgl=20
> depend on brl stuff? Maybe the necessary brl stuff could be moved=20
> into vpgl?
>
> Amitha.
>
> ----------------------------------------------------------------------
> --- This SF.net email is sponsored by: Microsoft Defy all challenges.=20
> Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl-maintainers@...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>
>
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Vxl-maintainers mailing list
Vxl-maintainers@...
https://lists.sourceforge.net/lists/listinfo/vxl-maintainers

I used bgeo in vpgl_camera_compute a few months ago when I updated the =
code there to work with satellite coordinates. I thought bgeo had been =
moved into vpgl_algo at some point but I guess it never made it. I'm =
not sure what else bgeo is used for in brl, maybe Gamze knows?
-Thom
=20
________________________________
From: Matt Leotta [mailto:matt.leotta@...]
Sent: Mon 11/19/2007 2:34 PM
To: Joseph Mundy; vxl-maintainers
Cc: Gamze Tunali; Pollard, Thomas
Subject: Re: FW: [Vxl-maintainers] BRL_INCLUDE_DIR
I think the culprit is actually vpgl_algo not vpgl. It looks like
vpgl_algo is linked to bnl_algo and bgeo. I know that bnl_algo is
used for my sparse levenberg marquardt implementation for bundle
adjustment. The sparse LM code is very general and should not moved
into vpgl. If anything it should be moved into vnl_algo. I can make
that move if there are no objections.
The actual error Fred is receiving comes from bgeo, which I don't know
anything about. Thom or Gamze would have to make the call on whether
or not it is appropriate to move that.
--Matt
On Nov 19, 2007 2:02 PM, Joseph Mundy <mundy@...> wrote:
> Matt, Thom,
> Is there something you use from brl in your vpgl stuff?
> If so maybe it can be moved to vpgl.
> Prof. Mundy
> -----Original Message-----
> From: vxl-maintainers-bounces@...
> [mailto:vxl-maintainers-bounces@...] On Behalf Of =
Amitha
> Perera
> Sent: Monday, November 19, 2007 11:32 AM
> To: Wheeler, Frederick W (GE, Research)
> Cc: vxl-maintainers@...
> Subject: Re: [Vxl-maintainers] BRL_INCLUDE_DIR
>
> I think you are correct about the build order affecting things. My
> guess is that most dashboard builds don't start from scratch each =
night.
>
> Brown folks: could you guys look into resolving this? Should vpgl
> depend on brl stuff? Maybe the necessary brl stuff could be moved =
into
> vpgl?
>
> Amitha.
>
> =
-------------------------------------------------------------------------=
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl-maintainers@...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>
>

I think the culprit is actually vpgl_algo not vpgl. It looks like
vpgl_algo is linked to bnl_algo and bgeo. I know that bnl_algo is
used for my sparse levenberg marquardt implementation for bundle
adjustment. The sparse LM code is very general and should not moved
into vpgl. If anything it should be moved into vnl_algo. I can make
that move if there are no objections.
The actual error Fred is receiving comes from bgeo, which I don't know
anything about. Thom or Gamze would have to make the call on whether
or not it is appropriate to move that.
--Matt
On Nov 19, 2007 2:02 PM, Joseph Mundy <mundy@...> wrote:
> Matt, Thom,
> Is there something you use from brl in your vpgl stuff?
> If so maybe it can be moved to vpgl.
> Prof. Mundy
> -----Original Message-----
> From: vxl-maintainers-bounces@...
> [mailto:vxl-maintainers-bounces@...] On Behalf Of Amitha
> Perera
> Sent: Monday, November 19, 2007 11:32 AM
> To: Wheeler, Frederick W (GE, Research)
> Cc: vxl-maintainers@...
> Subject: Re: [Vxl-maintainers] BRL_INCLUDE_DIR
>
> I think you are correct about the build order affecting things. My
> guess is that most dashboard builds don't start from scratch each night.
>
> Brown folks: could you guys look into resolving this? Should vpgl
> depend on brl stuff? Maybe the necessary brl stuff could be moved into
> vpgl?
>
> Amitha.
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl-maintainers@...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>
>

I think you are correct about the build order affecting things. My
guess is that most dashboard builds don't start from scratch each night.
Brown folks: could you guys look into resolving this? Should vpgl
depend on brl stuff? Maybe the necessary brl stuff could be moved into
vpgl?
Amitha.

VXL Maintainers:
I'm getting a few VXL build errors like the one below. This is the
first of about four similar ones. I'm stumped as to why I get these
errors on my local build but they don't show up on the dashboard.
Does anyone know why this might happen?
[ 90%] Building CXX object
contrib/gel/mrc/vpgl/algo/CMakeFiles/vpgl_algo.dir/vpgl_camera_compute.o
bj
vpgl_camera_compute.cxx
D:\home\wheeler\dev\vxl_src\contrib\gel\mrc\vpgl\algo\vpgl_camera_comput
e.cxx(25) : fatal error C1083: Cannot open include file:
'bgeo/bgeo_lvcs.h': No such file or directory
contrib/gel/mrc/vpgl/algo/vpgl_camera_compute.cxx #includes
bgeo/bgeo_lvcs.h. It seems to me that when
vpgl_camera_compute.cxx is compiled, the compiler would not know how
to find bgeo/bgeo_lvcs.h. The reason would be that
contrib/gel/mrc/vpgl/algo/CMakeLists.txt is visited by CMake before
contrib/brl/CMakeLists.txt, so BRL_INCLUDE_DIR is not yet defined when
it is used in contrib/gel/mrc/vpgl/algo/CMakeLists.txt.
Am I misunderstanding something? Is CMake run twice by all dashboard
builds? I know my nightly dashboard builds are set up to wipe the
build dir each time, so it would not be possible to "remember"
BRL_INCLUDE_DIR via the cache. I'm using cmake 2.4 under win2k.
Any ideas?
Thanks,
Fred

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details