Compiling cvi prj on visual studio

[moshoon]

hey

i am trying to set up a prj from cvi on vc 2010

after 2 whole days of breaking my head i reduced the number of error links to one:

SMB_Lib.lib(throughput.c) : error LNK2001: unresolved external symbol __shl64

i cant find a func by that name in the c source file(throughput.c)...so i cant trace it back to its source

i guess i am missing the shl64.obj and i cant find it anywhere-

btw i used these 2 ref:

http://zone.ni.com/reference/en-XX/help/370051T-01/cvi/programmerref/buildingprjinextcompiler/

and 

http://forums.ni.com/t5/LabWindows-CVI/Hot-to-create-a-CVI-2010-project-with-visual-studio-2010/m-p/...

which were great but i am missing the last peace of the puzzle

thanks

[Danceman]

Hello Moshoon,

      I have been racking my head trying to figure out what the shl64.obj does exactly.  With all LabWindows/CVI software installed I cannot find it on my machine either.  After researching it looks like you are missing a necessary object for 64 bit compilers to use Shell objects.  I wanted to let you know I am looking into this.  Have you found anything additional out in the mean time?

Daniel

[moshoon]

nothing

searched every file there

really lost!

and i am sure it is there, when i generate map file with cvi it shows up as linked

anyone?

[moshoon]

i found out another detail i think the shl64 has nothing to do with shells

it stands for shift left for 64 bit.

it is from the "family" of mul64 div64, etc- in this message : http://forums.ni.com/t5/LabWindows-CVI/Hot-to-create-a-CVI-2010-project-with-visual-studio-2010/m-p/...  LuisG supplies mul64 rol64 and ror64- 

i still cant get a hold of the shl64

[LuisG]

Moshoon,

As I mentioned in the other thread, it's error-prone to try to port CVI-built object files to VC because of implementation assumptions made by each compiler. I'll go ahead and attach the shl64 missing implementation here anyway, but a) this implementation was developed to be used by the CVI compiler, and it has only been tested in conjunction with the CVI compiler & linker, and b) you need to be aware that, with different versions of CVI or different versions of VC, this fix might no longer be sufficient.

Luis