On Thu, 30 Mar 2023 13:03:52 +0200
Tomas Hajny via fpc-pascal wrote:
>[...]
> I don't know where it is configured in Lazarus, but you need to use
> the -Xe parameter when using command-line compilation.
Project / Project Options / Compiler Options / All Options
Mattias
_
On 2023-03-30 10:08, Bo Berglund via fpc-pascal wrote:
On Thu, 30 Mar 2023 10:02:49 +0200, Tomas Hajny via fpc-pascal
wrote:
.
.
I'd suggest trying to switch to external linking (for both versions) -
that might help...
Could you be more specific?
I have never heard of such, I am just a
On Thu, 30 Mar 2023 10:02:49 +0200, Tomas Hajny via fpc-pascal
wrote:
>On 30 March 2023 9:36:35 +0200, Marco van de Voort via fpc-pascal
> wrote:
>>On 30-3-2023 07:38, Bo Berglund via fpc-pascal wrote:
>>> The problem seems to be that neither is a valid COFF file according to my
>>> Fpc
>>> (or
On 30 March 2023 9:36:35 +0200, Marco van de Voort via fpc-pascal
wrote:
>On 30-3-2023 07:38, Bo Berglund via fpc-pascal wrote:
>> The problem seems to be that neither is a valid COFF file according to my Fpc
>> (or Lazarus) in any case. Both generate the COFF error when reaching the
>> linker
>
On 30-3-2023 07:38, Bo Berglund via fpc-pascal wrote:
The problem seems to be that neither is a valid COFF file according to my Fpc
(or Lazarus) in any case. Both generate the COFF error when reaching the linker
step.
32-bit objs for delphi are typically OMF, 64-bit are typically coff (for
A
On Wed, 29 Mar 2023 19:27:12 -0400, Dennis Lee Bieber via fpc-pascal
wrote:
> I'd expect trying to link a 32-bit object file into a 64-bit
>application to result in all sorts of possible errors.
That is not the case here, they have supplied two obj files, one is 32 and the
other 64 bit.
Th
On Wed, 22 Mar 2023 14:17:23 +0100, Sven Barth via fpc-pascal
wrote:
>Then you should ask them for a suitable 64-bit object file (I assume that
>they'll provide the one for C which they probably also did for you back
>then and then you might need to adjust the import unit a bit to be usable
>with
On Wed, 22 Mar 2023 13:56:59 +0100, Bo Berglund via fpc-pascal
wrote:
>On Wed, 22 Mar 2023 12:33:16 +0100, Giuliano Colla via fpc-pascal
> wrote:
>
>>Il 22/03/2023 11:18, Bo Berglund via fpc-pascal ha scritto:
>>
>>> If I have fpc 3.2.2 inbstalled on Windows 10 x64 I assume it is a 64 bit
>>> ta
Bo Berglund via fpc-pascal schrieb am
Mi., 22. März 2023, 11:18:
>
> >The object file won't be a problem for FPC on i386-win32 because it will
> be
> >a COFF file which is the default.
>
> When you say "on i386-win32" does that mean a 32 bit version of Windows as
> the
> host system for building
Bo Berglund via fpc-pascal schrieb am
Mi., 22. März 2023, 13:57:
> On Wed, 22 Mar 2023 12:33:16 +0100, Giuliano Colla via fpc-pascal
> wrote:
>
> >Il 22/03/2023 11:18, Bo Berglund via fpc-pascal ha scritto:
> >
> >> If I have fpc 3.2.2 inbstalled on Windows 10 x64 I assume it is a 64
> bit targe
On Wed, 22 Mar 2023 12:33:16 +0100, Giuliano Colla via fpc-pascal
wrote:
>Il 22/03/2023 11:18, Bo Berglund via fpc-pascal ha scritto:
>
>> If I have fpc 3.2.2 inbstalled on Windows 10 x64 I assume it is a 64 bit
>> target
>> exe which will be the output, right?
>If in Project Options -> Config a
On Wed, 22 Mar 2023 12:33:16 +0100, Giuliano Colla via fpc-pascal
wrote:
>Il 22/03/2023 11:18, Bo Berglund via fpc-pascal ha scritto:
>
>> If I have fpc 3.2.2 inbstalled on Windows 10 x64 I assume it is a 64 bit
>> target
>> exe which will be the output, right?
>If in Project Options -> Config a
Il 22/03/2023 11:18, Bo Berglund via fpc-pascal ha scritto:
If I have fpc 3.2.2 inbstalled on Windows 10 x64 I assume it is a 64 bit target
exe which will be the output, right?
If in Project Options -> Config and Target ->Target OS you specify
Win32, you'll get a 32 bit exe (which is what Delph
On Wed, 22 Mar 2023 11:18:10 +0100, Bo Berglund via fpc-pascal
wrote:
>
>I guess I have to just create a simple program which reads the key data and
>does
>nothing else to check if the handling will actually work...
>Or convert a small tool we already have from Delphi7 to Lazarus/FPC and see
>w
On Wed, 22 Mar 2023 08:01:57 +0100, Sven Barth via fpc-pascal
wrote:
>Bo Berglund via fpc-pascal schrieb am
>Di., 21. März 2023, 23:54:
>
>> 1) How should I go about translating the above to current FreePascal
>> syntax?
>>
>> This involves:
>> { Force FAR calls }
>> {$F+}
>>
>> {$L SPROMEPS.OBJ
On Wed, 22 Mar 2023 00:19:58 +0100 (CET), Michael Van Canneyt via fpc-pascal
wrote:
>Maybe the THALES company has a 64-bit version of the .OBJ file.
OK, I will try and get some answers from them.
Problem is that they seem to have concentrated on Microsoft dev tools so lat
time I looked there was
Bo Berglund via fpc-pascal schrieb am
Di., 21. März 2023, 23:54:
> 1) How should I go about translating the above to current FreePascal
> syntax?
>
> This involves:
> { Force FAR calls }
> {$F+}
>
> {$L SPROMEPS.OBJ} { LINK WITH THE SUPERPRO OBJECT FILE }
>
These won't be a problem. Both Delphi
To: fpc-pascal@lists.freepascal.org
Sent: Tuesday, March 21, 2023, 23:49:30
Subject: [fpc-pascal] Converting Delphi7 code to FreePascal with interfacing to
protection key?
We have a number of old Delphi7 applications which are in need of porting over
to FreePascal. I have successfully done a number of
On Tue, 21 Mar 2023, Bo Berglund via fpc-pascal wrote:
We have a number of old Delphi7 applications which are in need of porting over
to FreePascal. I have successfully done a number of these ports in the last few
years...
But now I am up against a bit of a problem regarding software we have
We have a number of old Delphi7 applications which are in need of porting over
to FreePascal. I have successfully done a number of these ports in the last few
years...
But now I am up against a bit of a problem regarding software we have protected
using an USB connected hardware key originally boug
20 matches
Mail list logo
