RE: [Vxl-users] problems submitting nightly build with ctest for debug/release

[Wheeler, F. W \(Research\) <wh...@cr...>]

> I can do this... the only reasoning behind having both in the=20
> same build=20
> tree is that when I include the vxl libraries in my projects (using=20
> UseVXL.cmake in the CMakeLists.txt), the MSVS project built=20
> for my code=20
> includes the correct set of vxl libraries (debug or release) just by=20
> selecting debug/release in my project.

I can see how this would be nice, so hopefully you can get this working.

>  > It is also easier to keep a separate source tree for each=20
> dashboard=20
> build.
>=20
> I'm not sure I got this... Even if I don't modify the vxl=20
> source, should=20
> I still have separate source trees for each build? I thought nothing=20
> gets changed in the source tree by the build process...

The dashboard builds will cvs update the source tree, keep track of what =
files get updated, and report cvs updates and local file changes to the =
builds server.  If you do 2 builds off the same source tree, then they =
may try to cvs update the tree at the same time, or one will report the =
correct file updates for the day and the other will report no updates.  =
None of this is too big a deal as long as you are aware of these issues.

>  > By the way, I'm not sure whether you are implying this in=20
> your email,=20
> but I would not recommend doing development or making changes inside=20
> your dashboard build source trees.
>=20
> Again, I'm not modifying the vxl source tree. My source code=20
> uses vxl in=20
> a separate tree structure. However, this is something I'll=20
> keep in mind=20
> since I do look forward to adding my "two cents" to the vxl effort.

An advantage of keeping a separate source tree and build for your own =
work is that you can update it when you want, and when you see that the =
dashboard is reporting no errors.  If you use your automatic nightly =
build for your work then you might get stuck someday when some bad code =
gets checked in to cvs and your build is broken.  Even if everything =
works, trivial changes to the source may cause your own code to rebuild =
because libraries and header files have had their timestamp updated.

Fred Wheeler