[ome-users] Attempt to build "build-cpp"

[Roger Leigh]

On 10/05/2013 10:30, John Webber (NBI) wrote:
> Hi all,
> I am still experiencing the same error while trying to build a 64 bit,
> release version of the Omero CPPs.

> The error at the end of the
> “D:\GitHub\openmicroscopy_v4.4.7\components\tools\OmeroCpp\config.log”
> file is:
> C:\PROGRA~2\MICROS~2.0\VC\bin\link.EXE /nologo /MACHINE:X64 /DEBUG
> /OUT:.sconf_temp\conftest_2.exe /LIBPATH:.
> /LIBPATH:C:\Windows\Microsoft.NET\Framework64\v4.0.30319
> /LIBPATH:C:\Windows\Microsoft.NET\Framework64\v3.5 "/LIBPATH:C:\Program
> Files (x86)\Microsoft Visual Studio 10.0\VC\LIB\amd64"
> "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio
> 10.0\VC\ATLMFC\LIB\amd64" /LIBPATH:D:\GitHub\OMERO\lib
> /LIBPATH:D:\Ice\lib\vc100\x64 "/LIBPATH:C:\Program Files (x86)\Microsoft
> SDKs\Windows\v7.0A\lib\x64" /LIBPATH:D:\Ice\lib\x64 /LIBPATH:D:\Ice\lib
> Ice.lib .sconf_temp\conftest_2.obj
> .sconf_temp\conftest_2.obj : fatal error LNK1112: module machine type
> 'X86' conflicts with target machine type 'x64'
> scons: Configure: no
> As you can see, this STILL seems to be using D:\ice\lib in the LIBPATH,
> which is definitely incorrect!  However, this is NOT something that I am
> setting, so I don’t know where this is coming from.

Looking into our build scripts, it looks like this might actually be
being set by us during the build.  If you look at
components/blitz/blitz_tools.py, you should see a LIBPATH section with
the following logic:

         if ice_home:
             if self.is64bit():
                 if self.iswin32():
                     self.Append(LIBPATH=[os.path.join(ice_home, "lib",
"x64")])
                 else:
                     lib64 = os.path.join(ice_home, "lib64")
                     if os.path.exists(lib64):
                         self.Append(LIBPATH=[lib64])
             self.Append(LIBPATH=[os.path.join(ice_home, "lib")])

This can potentially set additional search paths depending upon the
platform/architecture in use.  If you delete the entirety of the above,
does the build then work?  You'll need to ensure that the proper path is
set in the LIBPATH environment variable.  The logic above might be
incorrect.  It's possible that this isn't the real cause of the problem
though--it might also be set somewhere else entirely.


Regards,
Roger

--
Dr Roger Leigh -- Open Microscopy Environment
Wellcome Trust Centre for Gene Regulation and Expression,
College of Life Sciences, University of Dundee, Dow Street,
Dundee DD1 5EH Scotland UK   Tel: (01382) 386364

The University of Dundee is a registered Scottish Charity, No: SC015096