[Insight-users] problem compiling ITK 3.20 for 64 bit targert on a WINXP 32 OS

[Robert Haase]

Hello François,

don't you see a way to compile on a x64 machine? If you're compiling a x64 version - there should be a computer to test it. Why not compiling on it? I'm using VS2008 and ITK on a Win XP x64 since years and it works fine. I'm not using the Express edition, but I think the compiler behind is equal. If the express edition turns out to be the source of the problem - you may try an evaluation edition of VS2008. Many universities are member of MSDA-AA, and so the costs of a non-Express VS edition should be minimal.

Regards,
Robert




-------- Original-Nachricht --------
> Datum: Thu, 31 Mar 2011 17:13:28 +0200
> Von: Francois DE VIEILLEVILLE <devieill at irit.fr>
> An: insight-users at itk.org
> Betreff: [Insight-users] problem compiling ITK 3.20 for 64 bit targert on a	WINXP 32 OS

> Hello all,
> 
> my problem seems rather common, but I cannot find the solution anywhere,
> so I am trying my luck over here !
> 
> * Brief description of the problem :
>  Compile ITK 3.20 for a 64 bit target (X64) with a VS 2008 Express 
> edition on a WIN 32 bit os :
> 
> * necessary steps
> 1) install win 7 sdk and SP1
> 2) patch so as to get the proper registry entries (otherwise x64 target 
> NEVER appears)
>     see 
> jenshuebel.wordpress.com/2009/02/12/visual-c-2008-express-edition-anb-64-bit-targets
> 3) configure cmake
> 4) launch VS2008, open ITK.sln file
> 5) configure Release X64
> 6) compile
> 
> * hard part
> Then the first problems appear :
> itkSysEncodeExecutable   :   in the "properties -linker-command line" 
> and extra parameter /machine:X86 appears and seems to contradict a 
> previous /machine:X64 option
> itkSysProcess   : same thing
> itkTestDriver : can't remember
> 
> tricky part :
> 
> if one enforces /machine:X64 then both sub-projects compile but  
> itkSysEncodeExecutable can never be called since it is not a VALID WIN 
> 32 app. COnsequences are that itksys lib sub-project can NEVER be 
> compiled as there is a call to the itkSysEncodeExecutable program.
> 
> possible solution :
> compile in 32 bit the 2 exe (itksysencode and itk sysProcess) and copy 
> the following executable from
> 
> /whatever/bin/Release/
> to /whatever/bin/x64/Release
> 
> 
> currently trying it, part of this  work (itkSys sub project compile) but 
> the ItkCommon.dll still cannot be produces...
> 
> 
> if anyone of you have the miracle solution,
> please share it !!!
> 
> Regards,
> 
> François
> 
> 
> 

-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!			
Jetzt informieren: http://www.gmx.net/de/go/freephone