Connecting Tech Pros Worldwide Help | Site Map

64-bit lib version for CPUInfo

=?Utf-8?B?amM=?=
Guest
 
Posts: n/a
#1: Oct 13 '08
Hello,

I am in process of porting a 32-bit app to a 64-bit app.
The 32-bit app compiles/links and executes OK using the
CPUInfo.lib. However, when I compile/link the 64-bit app
I get several unresolved linker errors. All of the linker
errors are related to the CPUInfo.lib:

error LNK2019: unresolved external symbol wincpuid
error LNK2019: unresolved external symbol wincpufeatures
error LNK2019: unresolved external symbol cpuspeed

Is there a 64-bit lib version of CPUInfo?

Thanks,
-jc
David Connet
Guest
 
Posts: n/a
#2: Oct 14 '08

re: 64-bit lib version for CPUInfo


=?Utf-8?B?amM=?= <jc@discussions.microsoft.comwrote in news:18B2BBB0-
ED59-4848-9158-A299D4A6B995@microsoft.com:
Quote:
Hello,
>
I am in process of porting a 32-bit app to a 64-bit app.
The 32-bit app compiles/links and executes OK using the
CPUInfo.lib. However, when I compile/link the 64-bit app
I get several unresolved linker errors. All of the linker
errors are related to the CPUInfo.lib:
>
error LNK2019: unresolved external symbol wincpuid
error LNK2019: unresolved external symbol wincpufeatures
error LNK2019: unresolved external symbol cpuspeed
>
Is there a 64-bit lib version of CPUInfo?
Check with the supplier. I don't think it's part of VC (at least it's
nowhere in my installation and about the only thing I don't have installed
is Crystal Reports)

Dave Connet
=?Utf-8?B?amM=?=
Guest
 
Posts: n/a
#3: Oct 14 '08

re: 64-bit lib version for CPUInfo




"David Connet" wrote:
Quote:
=?Utf-8?B?amM=?= <jc@discussions.microsoft.comwrote in news:18B2BBB0-
ED59-4848-9158-A299D4A6B995@microsoft.com:
>
Quote:
Hello,

I am in process of porting a 32-bit app to a 64-bit app.
The 32-bit app compiles/links and executes OK using the
CPUInfo.lib. However, when I compile/link the 64-bit app
I get several unresolved linker errors. All of the linker
errors are related to the CPUInfo.lib:

error LNK2019: unresolved external symbol wincpuid
error LNK2019: unresolved external symbol wincpufeatures
error LNK2019: unresolved external symbol cpuspeed

Is there a 64-bit lib version of CPUInfo?
>
Check with the supplier. I don't think it's part of VC (at least it's
nowhere in my installation and about the only thing I don't have installed
is Crystal Reports)
>
Dave Connet
>
Hi Dave,

Thank you for replying to my posting.
Yes, it is an Intel develped library.

-jc
David Connet
Guest
 
Posts: n/a
#4: Oct 19 '08

re: 64-bit lib version for CPUInfo


=?Utf-8?B?amM=?= <jc@discussions.microsoft.comwrote in
news:78C9964F-8FFB-44B4-836E-DECFC3DD2EDE@microsoft.com:
Quote:
>
>
"David Connet" wrote:
>
Quote:
>=?Utf-8?B?amM=?= <jc@discussions.microsoft.comwrote in
>news:18B2BBB0- ED59-4848-9158-A299D4A6B995@microsoft.com:
>>
Quote:
Hello,
>
I am in process of porting a 32-bit app to a 64-bit app.
The 32-bit app compiles/links and executes OK using the
CPUInfo.lib. However, when I compile/link the 64-bit app
I get several unresolved linker errors. All of the linker
errors are related to the CPUInfo.lib:
>
error LNK2019: unresolved external symbol wincpuid
error LNK2019: unresolved external symbol wincpufeatures
error LNK2019: unresolved external symbol cpuspeed
>
Is there a 64-bit lib version of CPUInfo?
>>
>Check with the supplier. I don't think it's part of VC (at least it's
>nowhere in my installation and about the only thing I don't have
>installed is Crystal Reports)
>>
>Dave Connet
>>
>
Hi Dave,
>
Thank you for replying to my posting.
Yes, it is an Intel develped library.
Then you need to get the x64 library from them. If there's not one
available, then you can't port to x64 - unless you remove the usage of
that library from you code.

Dave
Tamas Demjen
Guest
 
Posts: n/a
#5: Oct 20 '08

re: 64-bit lib version for CPUInfo


David Connet wrote:
Quote:
Then you need to get the x64 library from them. If there's not one
available, then you can't port to x64 - unless you remove the usage of
that library from you code.
Or make an out-of-proc COM object or command line EXE around the
function that only exists in 32-bit. That's a last resort possibility,
but it often works.

Tom
Closed Thread