Comments by SMDtheone

SMDtheone 5-Aug-22 16:48pm View

I see no problem here.
Bcc55 is a compiler, it deals with ones and zeros, I deal with the rest.

Windows is an operating system, which is comprised of built-in functions (kernel, UI, SDK).
Theoretically, those functions can be compiled into binary code even with a pencil and paper.

I am programming for fun, not for money. I love to learn what exactly is going on during the program execution, the stuff which "visual drag-and-droppers and C-sharpers" have no idea about :-)

SMDtheone 5-Aug-22 16:38pm View

All the computers I mentioned are Win 10/64.
I do not know if Win 10/32 even exists.
And all 32-bit software (usually found in "C:\Program Files (x86)" folder) runs perfectly fine on 64-bit hardware.

SMDtheone 5-Aug-22 0:53am View

Correction:
"...their static libraries do not contain any calls for DLLs on a given system" - which are not part of a standard Windows installation or their own software installation.

SMDtheone 5-Aug-22 0:46am View

Thank you, Dave!
Clarification:
My program is not using any DLLs. And I know for fact from the hardware manufacturer that their static libraries do not contain any calls for DLLs on a given system. The entire OEM-supplied SDK includes just two static libraries, one of which was mentioned in my original post. Of course, I can make a DLL version of each one of them, and see what happens (on my to-do list out of curiosity).
Win 10 does not give me an error, only a request for a missing DLL, and I am trying to understand why it needs a DLL for the code which has already been statically linked to the executable file.
The Dependency Walker is a new thing to me. I will see what it is, thank you very much!

SMDtheone 5-Aug-22 0:34am View

Thank you very much for your reply!
Just to clarify:
1) The application is 32 bit and the static libraries used (not DLLs) are all 32 bit. The 64-bit operating systems have no problem running 32-bit applications. The only thing in this combination is the presence of certain versions of Windows 10.
2) I recently installed a suite of the latest Borland IDE and the whole overhead that came with it. Guess what? The make file specifies the calls to the same command-line compiler and linker, each one only of a slightly higher version, with the same command-line parameters.
3) My business is in hardware control at the level of machine code, in real time. I write some subroutines in Assembly, and with that in mind, the farther I am from the abstractions brought in by the pure C++, C# or .NET framework, the better I feel :-)
4) I understand that modern OS can almost "disassemble" and scrutinize any file before permitting it to pass, for security reasons, but my program is not just getting blocked, it triggers a clear message about expecting dynamic libraries instead of static ones. And this is something new with Windows 10.
5) It is an interesting idea to "play" with a VM. I'll give it a try.

Comments by SMDtheone (Top 5 by date)