El 07/07/2018 a las 11:01, Bo Berglund escribió:
1) Include the DLL as a resource and extract it to a temp location
before loading it
I have seen these suggestions but the comments indicated that writing
a binary file to the filesystem on startup and then calling stuff
inside likely will
In our previous episode, Zoe Peterson said:
>
> There are a few options:
>
> 1) Include the DLL as a resource and extract it to a temp location ...
>
> 2) Load it directly from memory using a third party unit like this: ...
>
> 3) Codesign the DLL and executable and verify that they haven't
On Sat, 07 Jul 2018 03:04:21 -0500, "Zoe Peterson"
wrote:
>> Since this maker does not have an OBJ file to link with I thought I
>> would ask if it is possible to embed the DLL functionality directly
>> into the exe?
>
>There are a few options:
>
>1) Include the DLL as a resource and extract it
Zoe Peterson schrieb am Sa., 7. Juli 2018, 10:04:
>
> 3) Codesign the DLL and executable and verify that they haven't been
> modified. There's code to do that on Stack Overflow, though it wasn't
> tested on Lazarus:
> https://stackoverflow.com/questions/5993877/checking-digital-
>
> Since this maker does not have an OBJ file to link with I thought I
> would ask if it is possible to embed the DLL functionality directly
> into the exe?
There are a few options:
1) Include the DLL as a resource and extract it to a temp location
before loading it
2) Load it directly from
Is it possible to embed a DLL into the EXE file such that only the exe
needs to be distributed?
I need to use a 3rd party protection dongle in my programs. The maker
provides a DLL interface but it means that I must send this DLL along
with my program, which I would rather not do.
Previously we
