[Insight-developers] Fwd: [Vxl-users] vul_file.h bug

[Ho Cheung]

From: Ho Cheung <hocheung20 at gmail.com>
Date: Fri, Nov 11, 2011 at 12:16 PM
Subject: Fwd: [Vxl-users] vul_file.h bug
To: insight-developers at itk.org
Cc: Amitha Perera <amithaperera at users.sourceforge.net>, "
vxl-users at lists.sourceforge.net" <vxl-users at lists.sourceforge.net>,
yanggehua at gmail.com


Actually I found the problem now. It appears that my project is using the
vxl_config.h from the VXL that ITK includes with its own source as I
surmised earlier. Forwarding this to the ITK developer's list.


Ho Cheung
Research Assistant
Bio-Image Analytics Lab - University of Houston
hocheung20 at gmail.com
Cell: (832) 215-6347


On Fri, Nov 11, 2011 at 9:53 AM, Gehua Yang <yanggehua at gmail.com> wrote:

> If you look at line 125-139 in $vxl/src/CMakeLists.txt, you will see that
> VXL_USE_WIN_WCHAR_T is forced to be either 0 or 1  unless there is a
> situation that we missed.
>
> IF(WIN32)
>   IF(VXL_HAS_WIN_WCHAR_T)
>     OPTION( VXL_USE_WIN_WCHAR_T "Build overloading functions that accept
> Windows wide char strings?" YES )
>     IF(VXL_USE_WIN_WCHAR_T)   # Force it to be 0/1
>       SET(VXL_USE_WIN_WCHAR_T 1)
>     ELSE(VXL_USE_WIN_WCHAR_T)
>       SET(VXL_USE_WIN_WCHAR_T 0)
>     ENDIF(VXL_USE_WIN_WCHAR_T)
>   ELSE(VXL_HAS_WIN_WCHAR_T)
>     SET(VXL_USE_WIN_WCHAR_T 0)
>   ENDIF(VXL_HAS_WIN_WCHAR_T)
> ELSE(WIN32)
>   # avoid empty macro definition
>   SET(VXL_USE_WIN_WCHAR_T 0)
> ENDIF(WIN32)
>
> Second, you can look inside $vxl/bin/CMakeCache.txt, check what is the
> value of variable VXL_USE_WIN_WCHAR_T, making sure it is either 0 or 1.
>
> Third,  if both places look okay,  you will need to re-generate the
> vxl_config.h file.  You can do so by setting VXL_UPDATE_CONFIGURATION to
> true in CMake (note that it is an advanced variable) and hit Generate
> button.
>
>
> I believe these three steps will get you back on the road.  :)
>
> Best,
>
> Gehua
>
>
>
>
>
>
>
>
> On Thu, Nov 10, 2011 at 10:49 PM, Ho Cheung <hocheung20 at gmail.com> wrote:
>
>> Do you have any modified files in your VXL source tree?
>>>
>>
>> No.
>>
>>
>> Have you tried deleting your vxl_config.h from your build tree, and
>>> re-running CMake?
>>
>>
>> Yes. The problem still remains.
>>
>>
>> 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. :-/
>>>
>>
>> While vxl_config.h doesn't exist in our source tree, I noticed that ITK
>> uses its own internal version of VXL and has its own vul_config.h. I wonder
>> if this could be causing the issue.
>>
>>
>> Ho Cheung
>> Research Assistant
>> Bio-Image Analytics Lab - University of Houston
>> hocheung20 at gmail.com
>> Cell: (832) 215-6347
>>
>>
>> On Thu, Nov 10, 2011 at 9:31 PM, Amitha Perera <
>> amithaperera at users.sourceforge.net> wrote:
>>
>>>  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
>>> hocheung20 at gmail.com
>>> Cell: (832) 215-6347
>>>
>>>
>>> On Thu, Nov 10, 2011 at 6:20 PM, Peter Vanroose <
>>> peter_vanroose at yahoo.co.uk> wrote:
>>>
>>>> Ho Cheung <hocheung20 at gmail.com> 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 nowhttp://p.sf.net/sfu/rsa-sfdev2dev1
>>>
>>>
>>>
>>> _______________________________________________
>>> Vxl-users mailing listVxl-users at lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/vxl-users
>>>
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> RSA(R) Conference 2012
>> Save $700 by Nov 18
>> Register now
>> http://p.sf.net/sfu/rsa-sfdev2dev1
>> _______________________________________________
>> Vxl-users mailing list
>> Vxl-users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/vxl-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-developers/attachments/20120228/6367e3d7/attachment.htm>