I have a .f90 file and respective .dll from service provider. I am generating .dll using Intel Fortran Compiler from the source file (.f90) but it is not being loaded into the software (PSS Netomac). I am creating a 32bit .dll and the master copy is also a 32 bit.
Can somebody please suggest a possible solution / way of doing so? I am en electrical engineer and don't know much about programming..
Thanking in advance.
Related
Since the command-line tools x86_64-w64-mingw32-widl on Linux and widl on Windows both are able to produce type libraries, the .tlb files, for COM clients to import, it's reasonable to surmise that it might be doable to use MinGW toolset to build a COM client that is able to acquire COM interfaces by using smart pointers offered by the .tlb file, instead of calling function CoCreateInstance to get the interfaces. The question is how?
Visual C++ has its nonstandard directive #import to introduce the smart pointer types (and other stuff) to C++ code. What is the counterpart when we are using MinGW g++?
By the way, I've been googling all day and found it difficult to find useful information about "MinGW + COM". Most of them use Visual C++. If you know somewhere out there a good online tutorial on this topic is, please let me know. Thanks.
I have a dll file that has been created and compiled with C++ under Windows and I unfortunately don't have the source code for it.
This dll file is working well with a .NET program compiled with visual studio.
I want to know if this is possible to import this dll file with mono, and execute it under a UNIX environment.
This dll file is sending some Smartcard APDU instructions.
Most probably no. Binaries are platform specific.
You can always try to disassemble it on Windows and try to compile the disassembled code on unix, however I think it's not worth it.
I want to know which compiler I can use to create a .dll file from a .C file.
I cant find any tutorial how to create a .dll file from a C file.
I am new to creating dll files . Please help
Thanks in advance
You mention that you want to create a DLL from a .C file. Just to clarify, are you using C (.c file) or C++ (.cpp) to write your code?Also, if you are using C++, are you using Visual Studio?
If you are using C: National Instruments provides an ANSI C Application Development Environment called LabWindows/CVI which makes building dlls a snap. It has templates for DLLs and you can build them either as stdcall or cdecl dlls.
Building a DLL with LabWindows/CVI 8.5 for use with LabVIEW 8.5
If you are using Visual C++: Look at the link that Al provided earlier.
Walkthrough: Creating and Using a Dynamic Link Library (C++)
If you aren't using CVI or Visual Studio, then really the best bet is to do a google search for "Create C DLL".
I would suggest if you have .C file go with Eclipse
EDITED
Eclipse Managed Build
+
Shared libraries with Eclipse CDT and cygwin on Windows
On Linux platforms you need only the .so file when you want to implicitly link to it.
Why Microsoft developed the approach where you need a .lib file also. Doesn't the DLL contain all the information for the linker to be able to link to it?
From my experience the "Windows way" is more clumsy and creates problems when you want to mix different compilers and linkers.
I am currently working on an iOS project using the Unity framework.
When I export an Xcode project from Unity, there are a whole bunch of files exported.
Besides some source files, there are also .dll files for the Mono project.
But there are also .dll.s files.
For troubleshooting, it would be great to know what they are used for.
There is one .dll.s file for every dll, so it could be some sort of source which is compiled into the dll?
When there are exceptions somewhere in the code, Xcode often jumps into one of these .dll.s files and it looks as if they contain some sort of assembly code.
Directions would be nice, Google isn't really helpful here ...
TIA,
best regards,
Flo
They're the IL code in the dll files compiled into arm assembly. This is the code that eventually end up in the final app binary.