Help with x64: fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

Question

Hello, I am trying to complie some C code for some applications I am working on in labview (I am using Labview 2012 64bit).
When I try to build my code in Visual C++ 2010 ( I have set it up to be able to use x64) I get the following fatal error:
nivision.lib(StartupShutdown.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
Which I understand that .lib does not have a 64bit compatability. However, if I were to use 32bit code, how can I link/emulate it to my 64bit labview? Is there a good tutorial on this application? The problem is the rest of my application uses and requires 64bit labview, so I am stuck in this enviroment.
Thanks.

Answer 1

dbrittain wrote:
Thanks for the reply. The C code I have cross correlates images, and it does reference the image inputs and size variables from the nivision classes. I am thinking of using a side by side labview environment with shared variables. I have not done this before, do you have any good examples? Can you make the library function node a shared variable or only the elements within it? 
I guess I could try to convert to labview, but the are a lot of lines of code that I would prefer not to try to wrap my head around in translation.
The LabVIEW API in Vision Development Module has functions that let you get access to all those parameters as well as the raw image data pointer. A common design is to query those items on the LabVIEW diagram and then pass them to your DLL. This would mean you wouldn't need to make any calls into the Vision DLL from your C code.
As for examples showing how to use shared variables, keep in mind that it isn't just like doing a function call. The more appropriate way to think of it would be communicating with another VI by getting and setting controls and indicators while it runs. You could put all your arguments into a shared variable and set a boolean indicating it is ready, then wait for another boolean to go high indicating the other code has finished and placed its results in another shared variable. Your application code interacts with the shared variables just like a control/indicator/local variable. This of course is a simple description and I would not be surprised if there are well-defined frameworks/examples searchable in the forums that use shared variables in this manner.
Eric
Eric