Forum > Windows
optimized sources
_heinz:
--- Quote from: Jason G on 30 Oct 2008, 12:22:09 pm ---Heinz, 2.2 is too old. Though I can't read the German errors I would avoid older versions (that old) like the plague because of Boincapi, compiler, and target platform changes. please consider starting with AK_v8 build as we tried to make it much easier. simply changing the ICC & IPP directories (in the project includes and linker linraiy paths) should allow you to build against our boincapi. If you need some help let me know, as I am coming to some heavy multithreaded opportuntities and would like you to be up to speed for some collaboration.
Jason
--- End quote ---
on my old xp-machine this older version 2.2 compiles complete without error. So I thought it is a good complete test.
The problem is perhaps the following: OS is Vista64, compile a program as 32 bit program
libcpmtd.lib(iostream.obj) : fatal error LNK1112: Modul-Computertyp "IA64" is in conflict with goal-computertyp "X86".
--------------------------------------------------------------
In the SDK Realease notes we found:
Visual C++® Search Paths and Registering Environment Variables
Selecting to Register Environment Variables places the Platform SDK bin, include, and library directories at the beginning of the search paths used when building programs in the Visual Studio IDE.
Note To target a specific version of Windows, you must still define the _WIN32_WINNT, _WIN32_IE, and _WIN32_WINDOWS macros as appropriate.
To register the SDK bin, include, and library directories with Microsoft Visual Studio® version 6.0 and Visual Studio .NET, click Start, point to All Programs, point to Microsoft Platform SDK for Windows Server 2003 SP1, point to Visual Studio Registration, and then click Register PSDK Directories with Visual Studio. This registration process places the SDK bin, include, and library directories at the beginning of the search paths, which ensures that the latest headers and libraries are used when building applications in the IDE.
Note that for Visual Studio 6.0 integration to succeed, Visual Studio 6.0 must run at least once before you select Register PSDK Directories with Visual Studio. Also note that when this option is run, the IDEs should not be running.
To develop a 32-bit C/C++ application on 64-bit Windows, do not register environment variables when you install Visual C++ 6.0. Instead, open a command window and run Vcvars32.bat (from the Visual C++ \bin folder), followed by Setenv.bat (from the SDK bin folder), specifying the appropriate switches (such as /SVR32 /2000 /XP32).
Maybe this is the problem
did you remember todo so Jason?
some other projects(arprec) I tried did not have this problem... will try some others now too
with akv8 I believe I must use IPP5.3, have still 5.2beta.
there is still something to install (ITBB and latest IPP)
_heinz:
Looked up for the link error and found:
Linker Tools Error LNK1112
The object files specified as input were compiled for different computer types.
libcpmtd.lib(iostream.obj) : fatal error LNK1112: Modul-Computertyp "IA64" is compiled for IA64, but should for x86
hmm.....
look as a error in the environment... ?
----------------------------------------------------
The Platform SDK 64-bit build tools use a version of CRT that still has support for the older style iostream.h, (iostream.h is no longer supported in Visual Studio 2003. Visual Studio 2003 supports iostream instead.) As a consequence of this, there are some samples in the PSDK, using iostream.h that build for 64-bit Windows platforms, but not for 32-bit platforms.
looks like using old iostream headers here
maybe this is the error ?
heinz
_heinz:
set the environment
but no possibility to do this for Vista64, not in script...
REM "Usage: Setenv [/2000 | XP32 | /XP64 | /SRV32 | /SRV64 | /X64] [/DEBUG | /RETAIL]"
REM
REM /2000 - target Windows 2000 and IE 5.0
REM /XP32 - target Windows XP 32 (default)
REM /XP64 - target Windows XP 64
REM /SRV32 - target Windows Server 2003 32 bit
REM /SRV64 - target Windows Server 2003 64 bit
REM /X64 - target Windows for the X64 bit platform
REM /DEBUG - set the environment to DEBUG
REM /RETAIL - set the environment to RETAIL
-----------------------------------------------------------------------------------
C:\I\SDK>SetEnv /X64
Targeting Windows Server 2003 X64 DEBUG
C:\I\SDK>SetEnv /SRV64
Targeting Windows Server 2003 IA64-bit DEBUG
---------------------------------------------------------------------------------
there is vcvarsall.bat -->
@echo off
if "%1" == "" goto x86
if not "%2" == "" goto usage
if /i %1 == x86 goto x86
if /i %1 == amd64 goto amd64
if /i %1 == x64 goto amd64
if /i %1 == ia64 goto ia64
if /i %1 == x86_amd64 goto x86_amd64
if /i %1 == x86_ia64 goto x86_ia64
goto usage
:x86
if not exist "%~dp0bin\vcvars32.bat" goto missing
call "%~dp0bin\vcvars32.bat"
goto :eof
:amd64
if not exist "%~dp0bin\amd64\vcvarsamd64.bat" goto missing
call "%~dp0bin\amd64\vcvarsamd64.bat"
goto :eof
:ia64
if not exist "%~dp0bin\ia64\vcvarsia64.bat" goto missing
call "%~dp0bin\ia64\vcvarsia64.bat"
goto :eof
:x86_amd64
if not exist "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat" goto missing
call "%~dp0bin\x86_amd64\vcvarsx86_amd64.bat"
goto :eof
:x86_ia64
if not exist "%~dp0bin\x86_ia64\vcvarsx86_ia64.bat" goto missing
call "%~dp0bin\x86_ia64\vcvarsx86_ia64.bat"
goto :eof
:usage
echo Error in script usage. The correct usage is:
echo %0 [option]
echo where [option] is: x86 ^| ia64 ^| amd64 ^| x86_amd64 ^| x86_ia64
echo:
echo For example:
echo %0 x86_ia64
goto :eof
:missing
echo The specified configuration type is missing. The tools for the
echo configuration might not be installed.
goto :eof
-----------------------------------------------------------------
and now call vcvarsall.bat
C:\Program Files (x86)\Microsoft Visual Studio 8\VC>vcvarsall.bat ia64
The specified configuration type is missing. The tools for the
configuration might not be installed.
try then this -->
C:\Program Files (x86)\Microsoft Visual Studio 8\VC>vcvarsall.bat
Setting environment for using Microsoft Visual Studio 2005 x86 tools.
hmmm....
we will se if it works on Vista64
the arprec project I can compile sucessful with VS2005 Express
the old 2.2 shows the same link error as before with VS2008 Express....
tried to compile a project which has asm source and it fails with VS2008 Express...
with VS2005 Express the asm works correct.....hmmmm
any ideas ?
heinz
heinz
Jason G:
Try this one Heinz:
--- Quote ---REM /X64 - target Windows for the X64 bit platform
--- End quote ---
_heinz:
Had have a look at the system variables of Vista64 and wounder what I found there:
NUMBER_OF_PROCESSORS 8
PROCESSOR_ARCHITECTURE AMD64
PROCESSOR_IDENTIFIER Intel64 Family 6 Model 23 Stepping 6, GenuineIntel
PROCESSOR_LEVEL 6
PROCESSOR_REVISION 1706
----------------------------------------------------------------------------
If I look at the package of the Processor E5405 we see:
Quad-Core
Intel Xeon Processor 5400 Series
QUOAD-CORE SERVER
Intel Core Microarchitecture
Support for Two-Socket Systems
Intel 64 Architecture
Intel Virtualization Technology
--------------------------------------------------
and Everst shows:
Computertyp ACPI x64-basierter PC
Betriebssystem Microsoft Windows Vista Ultimate
.....
Motherboard
CPU Typ 2x QuadCore Intel Xeon E5405, 2400 MHz (6 x 400)
Motherboard Name Intel Skulltrail D5400XS (2 PCI, 4 PCI-E x16, 4 FB-DIMM, Audio, Gigabit LAN)
Motherboard Chipsatz Intel Seaburg 5400B
Arbeitsspeicher [ TRIAL VERSION ]
Channel0-DIMM1: Kingston 4 GB DDR2-800 ECC DDR2 SDRAM FB-DIMM (4-4-4-15 @ 320 MHz) (5-5-5-18 @ 400 MHz)
Channel1-DIMM1: Kingston 4 GB DDR2-800 ECC DDR2 SDRAM FB-DIMM (4-4-4-15 @ 320 MHz) (5-5-5-18 @ 400 MHz)
BIOS Typ Intel (08/25/08)
---------------------------------------------
I cant believe it, Vista 64 shows PROCESSOR_ARCHITECTURE AMD64 :o
heinz
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version