DLL, Import = "invalid machine type" for one exe only

[jassing]

I have a project that consists of a few exe's and one dll.
All the exe's use the dll.
All exe's build fine, except one.
When I build it; I'm told that the dll has an invalid machine type.



Just "Import mydll.dll/endimport" will trigger the error. Including one or 20 definitions in the import block doesn't matter -- always gets the "Invalid machine type".

I have rebooted, moved the project (one post said it was a rights issue), created another admin user (I am admin on my machine) -- still happens.

Is there any way to figure out why this one exe doesn't like the dll?
The dll works fine: I have this code (to easily switch back and forth):

Code: Select all

CompilerIf #False
Import "InstTK.dll"
	GetMSSQLServers(nIndex = -1)
EndImport
CompilerElse
	Prototype ptGetMSSQLServers(nIndex=-1)
	hDLL = OpenLibrary(#PB_Any,"Insttk.dll")
	Global GetMSSQLServers.ptGetMSSQLServers = GetFunction(hDLL,"GetMSSQLServers")
CompilerEndIf

So I can use the dll w/o issue. (the exe runs fine & works as expected)
Even if I comment out the call to the dll function, and include no functions, ie:

Code: Select all

Import "InstTK.dll"
EndImport

Will generate the error. Other exe's that include the import build fine.

[ts-soft]

You have to import the "InstTK.lib" or OpenLibrary "InstTK.dll"

[jassing]

You have to import the "InstTK.lib" or OpenLibrary "InstTK.dll"

HAHAHAHHAHA!! Thanks.
I started having problems about 5am; I should have said "get some rest" -- for hte life of me, I couldn't see that I was using .dll...
Sometimes I wonder how I get out of bed. thanks.

[ozzie]

Thanks - I tripped over the same issue with importing. Was very glad to find the answer on the Forum.

[Niffo]

And how to do the same for MacOS ? PB for MacOS generates ".so" files when compiling as "Shared DynLib". But importing this file with "Import" causes a linker error.

[jack]

I jus tried it on my Mac and it work OK