Re: [Vxl-users] vul_file.h bug

[Amitha P. <ami...@us...>]

In a different email to me, you said you are using r32878.  There was an 
issue initially, but it was fixed in r26761 for Windows, and r26820 for 
all platforms.

Do you have any modified files in your VXL source tree?

Have you tried deleting your vxl_config.h from your build tree, and 
re-running CMake?

Also make sure you don't have a vxl_config.h in your *source* tree. This 
can happen if the user accidently does an in-source configuration. If 
this happens, it's very difficult to undo. :-/

Amitha.


On 11/10/2011 10:14 PM, Ho Cheung wrote:
> That is what we have been doing. However, this is not a very good fix 
> because we would like to have an automated way to build everything.
>
> Does anyone understand what the issue causing VXL_USE_WIN_WCHAR_T not 
> to be defined to 0 or 1 is?
>
> Ho Cheung
> Research Assistant
> Bio-Image Analytics Lab - University of Houston
> hoc...@gm... <mailto:hoc...@gm...>
> Cell: (832) 215-6347
>
>
> On Thu, Nov 10, 2011 at 6:20 PM, Peter Vanroose 
> <pet...@ya... <mailto:pet...@ya...>> wrote:
>
>     Ho Cheung <hoc...@gm... <mailto:hoc...@gm...>> wrote:
>
>     > This is at the bottom of vxl_config.h:231:
>     >
>     > #define VXL_USE_WIN_WCHAR_T
>
>     In that case, the easiest fix is to manually add "0" at the end of
>     this line.
>
>     --        Peter.
>
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
>
>
> _______________________________________________
> Vxl-users mailing list
> Vxl...@li...
> https://lists.sourceforge.net/lists/listinfo/vxl-users