The VXL Project

Brendan,

  I run that dashboard build.  The errors are all coming from the
recently added wxWidgets support in vgui by Miguel.  The errors will
all go away if I turn off wxWidgets in CMake.  Miguel said this might
be related to unicode support compiled into wxWidgets.  I'm using a
stock wxWidgets package from Debian, so I would imagine this problem
is more wide spread.  I think most Dashboard builds either don't have
wxWidgets or it is disabled in the CMake cache, so it is hard to tell
for sure.

  In my opinion these are not critical errors, and you should probably
go ahead with the release.  However, you might want to get feedback
from Miguel first.  He said he was going to look into the problem.

Thanks,
Matt Leotta

On 7/26/06, Brendan McCane <mccane@...> wrote:
> G'day Maintainers,
>
> I notice that there are a bunch of build errors on the lems.=ADbrown.=ADe=
du
> Linux-2.=AD6_=ADem64t_=ADgcc-4.=AD0.=AD3_=AD-Wall build. Are these critic=
al errors
> or something specific to that setup? Should I ignore them and make a
> release anyway? Or is someone looking into them?
>
> --
> Cheers,
>
> Brendan.
> -------------------------------------------------------------------------=
---
> Brendan McCane                            Email:  mccane@...
> Department of Computer Science            Phone:  +64 3 479 8588/8578.
> University of Otago                       Fax:    +64 3 479 8529
> Box 56, Dunedin, New Zealand.
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Vxl-maintainers mailing list
> Vxl-maintainers@...
> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers
>

> On 7/26/06, Brendan McCane <mccane@...> wrote:
> > G'day Maintainers,
> >
> > I notice that there are a bunch of build errors on the lems.=ADbrown.=
=ADedu
> > Linux-2.=AD6_=ADem64t_=ADgcc-4.=AD0.=AD3_=AD-Wall build. Are these crit=
ical errors
> > or something specific to that setup? Should I ignore them and make a
> > release anyway? Or is someone looking into them?
>
On 7/28/06, Matt Leotta <matt.leotta@...> wrote:
>   I run that dashboard build.  The errors are all coming from the
> recently added wxWidgets support in vgui by Miguel.  The errors will
> all go away if I turn off wxWidgets in CMake.  Miguel said this might
> be related to unicode support compiled into wxWidgets.  I'm using a
> stock wxWidgets package from Debian, so I would imagine this problem
> is more wide spread.  I think most Dashboard builds either don't have
> wxWidgets or it is disabled in the CMake cache, so it is hard to tell
> for sure.
>
>   In my opinion these are not critical errors, and you should probably
> go ahead with the release.  However, you might want to get feedback
> from Miguel first.  He said he was going to look into the problem.

The problem is that the wxWidgets lib that Matt's build is using has
unicode support built in. These incompatibilities should be pretty
easy to fix, but I can't work on this right now as I am in the middle
of reallocating. Probably by the end of august I will have a setup to
work on this. I don't know to what extent Amitha is working on it. He
submitted a patch related to this yesterday, but there is more work to
be done.

These are all compile time errors, which I am able to pick up and work
on because of the dashboard. However, I expect that there are some
run-time issues with other platforms than Windows, since I have only
tested in the windows platform up to now. This is also something I
will put some effort into after I settle down (debugging in a Linux
platform).

That said, I agree with Matt that these are not critical errors and
that the release should be made. There is an option to turn vgui_wx
off in the cmake GUI and the default toolkit is not wxWidgets, but
usually gtk or mfc. The only thing that might be appropriate is to
turn the VGUI_USE_WX OFF by default on this release.

--Miguel

On Fri 28 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> I don't know to what extent Amitha is working on it.

Not much, I'm afraid. It'd be good to get it working, but time is
always limited...

> The only thing that might be appropriate is to turn the VGUI_USE_WX
> OFF by default on this release.

I'd agree with this. Let's keep the support in there, and turn it off
by default since it doesn't work everywhere. Miguel: maybe you want to
quickly add a line to CHANGES.txt saying vxl now has preliminary
wxWidgets support?

Amitha.

On 7/31/06, Amitha Perera <perera@...> wrote:
> On Fri 28 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> > The only thing that might be appropriate is to turn the VGUI_USE_WX
> > OFF by default on this release.
>
> I'd agree with this. Let's keep the support in there, and turn it off
> by default since it doesn't work everywhere. Miguel: maybe you want to
> quickly add a line to CHANGES.txt saying vxl now has preliminary
> wxWidgets support?

OK, I set VGUI_USE_WX to OFF by default and added the following line
to CHANGES.txt (feel free to edit as you like):

- VXL's GUI Library (vgui) now has preliminary support for wxWidgets
as the rendering toolkit. It has been tested only in Windows
platforms and has known problems with UNICODE builds of wxWidgets
(to be solved in a later release). To turn-on compilation of the
wxWidgets support set the VGUI_USE_WX option in CMake to ON (OFF
by default).

--Miguel

On Mon 31 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> OK, I set VGUI_USE_WX to OFF by default [...]

Except that'd cause the dashboards not to build wx too. I guess we can
set it back after Brendan makes the release.

Amitha.

I think VGUI_USE_WX was initially set to OFF by default which caused
the dashboards to not build wx.  It was then changed to ON, but by
then most dashboard builds already had OFF in their cache.  I turned
it on manually in my dashboard build which caused the errors in
question.  So not only do we need to change in back to ON after the
release, but we should also reset this cached value in at least some
of the builds to get better coverage on the dashboard.

--Matt

On 7/31/06, Amitha Perera <perera@...> wrote:
> On Mon 31 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> > OK, I set VGUI_USE_WX to OFF by default [...]
>
> Except that'd cause the dashboards not to build wx too. I guess we can
> set it back after Brendan makes the release.
>
> Amitha.
>

> On 7/31/06, Amitha Perera <perera@...> wrote:
> > On Mon 31 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> > > OK, I set VGUI_USE_WX to OFF by default [...]
> >
> > Except that'd cause the dashboards not to build wx too. I guess we can
> > set it back after Brendan makes the release.

This sounds good to me. I'll re-enable it after the release.

On 7/31/06, Matt Leotta <matt.leotta@...> wrote:
> I think VGUI_USE_WX was initially set to OFF by default which caused
> the dashboards to not build wx.  It was then changed to ON, but by
> then most dashboard builds already had OFF in their cache.  I turned
> it on manually in my dashboard build which caused the errors in
> question.  So not only do we need to change in back to ON after the
> release, but we should also reset this cached value in at least some
> of the builds to get better coverage on the dashboard.
>
> --Matt

Is there a way to force a value in the cache of the dashboard builds?
or to delete the cache and reconfigure? IIRC, I had problems with
DirectShow related errors popping up long after committing them, when
the build was re-configured. The only thing I can think of right now
is to temporarily add a line like:

SET(VGUI_USE_WX ON CACHE INTERNAL "Forcing the value.")

or

SET(VGUI_USE_WX ON CACHE BOOL "Forcing the value." FORCE)

to the CMakeLists.txt. Then remove it after a day or so to allow users
to override it.


--Miguel

On Mon 31 Jul 2006, Miguel A. Figueroa-Villanueva wrote:
> The only thing I can think of right now
> is to temporarily add a line like:
> 
> SET(VGUI_USE_WX ON CACHE INTERNAL "Forcing the value.")
> 
> or
> 
> SET(VGUI_USE_WX ON CACHE BOOL "Forcing the value." FORCE)
> 
> to the CMakeLists.txt. Then remove it after a day or so to allow users
> to override it.

I think this is okay. Note that some of the dashboards, such as those
that Fred Wheeler submits (crd.ge.com), start from an empty build
directory every night; they won't need this, but others may.

Amitha.