LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

building 64-bit static lib

I'm trying to update the ReadSaveJpeg library for 64-bit.  I created a new project, attached these files and set it up for a 64-bit build, all default settings (whose build options compiler defines are set to /DWIN32_LEAN_AND_MEAN).

 

The first attempt generated a *.lib file that was in fact still 32-bit though I was using the Release64 build output.  I know this because in my project that uses this library, CVI is graying out the file and considers it 32-bit:

 

outputted lib is actually 32-bitoutputted lib is actually 32-bit

So then I played with the build compiler options, guess on a /_NI_x64_. This resulted in a much larger lib file which was then properly identified as 64-bit:

 

2019-06-19 12_08_58-c__..._SVN Checkouts_XRF Source Driver_XRF Source DLL.cws.png

 

However, compiling my main application with Release64 gives me either 32-bit warnings or "input file not a valid archive" errors.

0 Kudos
Message 1 of 2
(2,247 Views)

Hi,

I haven't found much about this error in my own searching. If you have a support account, it might be worthwhile to talk to our support team about this, since it seems like a fairly complex problem. I did find someone finding some success with overcoming that type of error by changing the .lib to a dll, but I'm not sure that would be a feasible solution in your application.

 

Thanks, 

 

ZofiaK

 

 

Zofia
NI Technical Support Engineer
Message 2 of 2
(2,209 Views)