DLL interface problem

[vhdl]

Dear LabVIEW fans

I have a problem building an exe file for a windows ce 5.0 system. I can build LabVIEW apps for my windows ce 5.0 device with the touchpanel module but I have problems integrating a dll with it.

The lib file is included.

It's targetted for an ARM processor

Code is developed in LV 2009 SP1 with Touchpanel module.

Very much thank you!

LaVAGQuestion.zip

[Rolf Kalbermatter]

Dear LabVIEW fans

I have a problem building an exe file for a windows ce 5.0 system. I can build LabVIEW apps for my windows ce 5.0 device with the touchpanel module but I have problems integrating a dll with it.

The lib file is included.

It's targetted for an ARM processor

Code is developed in LV 2009 SP1 with Touchpanel module.

Very much thank you!

TcAdsDll.dll is definitly an x86 shared library and as such not loadable on an ARM or RISC Windows CE system. A quick Hex Editor look at TcAdsDllCe.lib seems to show that it references the TcAdsDllCe.dll and as you can see that is different than the TcAdsDll.dll you have in that archive.

Also I'm not sure you do need the lib file at all when porting a LabVIEW library from your host system to an emebedded device. The normal opeation is to create a stub shared library for your host platform (Windows development machine) that has the same name and exports empty functions of all the functions you want to use in your embedded target LabVIEW application. Then you create Vis accessing this stub library through the Call Library Node.

In this particular case you may even be able to skip the creation of the stub shared library and simply rename the Windows TcAdsDll.dll to TcAdsDllCe.dll to create on your Windows system the VIs to deploy to your embedded target. You still will have to make sure to deploy the shared library to your target that is compatible with your target and not your renamed fake DLL. This renaming could however fail in some ways if the DLL internally has code that somehow relies on its own name.

Maybe you are going this in a completely different way that I'm not familiar with, such as the C inline node, but then you still will need to make sure you use the right shared library that matches your import library.

[vhdl]

Thanks for the tips

Going to give it a try

[vhdl]

Thanks for the tips

Going to give it a try

I can't get it to function.

[Rolf Kalbermatter]

I can't get it to function.

And I don't have psychic powers to see what you are doing so I can't give you any advice here!

[vhdl]

I did a new try.. Still nothing. (see atachment)

testdgvdt.zip

[vhdl]

I did a new try.. Still nothing. (see atachment)

When I change everything to x86 system (still windows CE 5.0) everything is compiling and my emulator with windows CE shows me the expected result...

[vhdl]

When I change everything to x86 system (still windows CE 5.0) everything is compiling and my emulator with windows CE shows me the expected result...

This is the error I get in my log:

Untitled_1.c

Generating Code...

Compiling...

_lvcepda80ARMtemp_.cpp

Generating Code...

Compiling...

lvCEPDAMain.c

Generating Code...

PDALib0.lib(TcAdsDllCe.DLL) : fatal error LNK1112: module machine type 'THUMB' conflicts with target machine type 'ARM'

Searching for it gives me the following link

http://social.msdn.microsoft.com/forums/en-US/windowsmobiledev/thread/34907fec-3ff2-453b-ad16-5a6de7e01169/

Any advice?

[vhdl]

This is the error I get in my log:

Untitled_1.c

Generating Code...

Compiling...

_lvcepda80ARMtemp_.cpp

Generating Code...

Compiling...

lvCEPDAMain.c

Generating Code...

PDALib0.lib(TcAdsDllCe.DLL) : fatal error LNK1112: module machine type 'THUMB' conflicts with target machine type 'ARM'

Searching for it gives me the following link

http://social.msdn.m...6-5a6de7e01169/

Any advice?

Any chance when I edit C:\Program Files\National Instruments\LabVIEW 2009\PDA\Utilities script files?

[vhdl]

could it be possible because my target is ARMV4I and labview tries to compile for ARMV4?