64-bit lib version for CPUInfo

  • Thread starter Thread starter jc
  • Start date Start date
J

jc

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
 
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?
Click to expand...

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
 
David Connet said:
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
Click to expand...

Hi Dave,

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

-jc
 
Hi Dave,

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

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
 
David said:
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.
Click to expand...

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
 
Back
Top