On 07/27/2018 02:36 AM, Bo Berglund via Lazarus wrote:
...
And we have had lots of problems over the years with their dongle
driver for Windows.
Thankfully we've not experienced that.
Thanks Bo for your comments!
Regards,
Paul
www.ControlPascal.com
--
_
On Wed, 25 Jul 2018 13:31:08 -0400, Paul Breneman via Lazarus
wrote:
>I need to use the *same* security dongle in Lazarus. I don't want to
>change to a different dongle.
Since Safenet does not provide any new OBJ file n´than the one fpc
cannot use the only path seems to be to somehow convert i
On 06/20/2018 01:54 AM, Bo Berglund via Lazarus wrote:
On Wed, 13 Jun 2018 10:29:05 +0200, Michael Schnell via Lazarus
wrote:
On 12.06.2018 17:08, Sven Barth via Lazarus wrote:
No. Delphi does *not* solve this by using dynamic linking.
OK. I see. Thanks for pointing this out.
Hence in such
On Wed, 13 Jun 2018 10:29:05 +0200, Michael Schnell via Lazarus
wrote:
>On 12.06.2018 17:08, Sven Barth via Lazarus wrote:
>> No. Delphi does *not* solve this by using dynamic linking.
>OK. I see. Thanks for pointing this out.
>
>Hence in such a (potentially problematic) case the suggested soluti
On 12.06.2018 17:08, Sven Barth via Lazarus wrote:
No. Delphi does *not* solve this by using dynamic linking.
OK. I see. Thanks for pointing this out.
Hence in such a (potentially problematic) case the suggested solution
might be helpful even with Delphi.
But as Bo's code seemingly works fin
Michael Schnell via Lazarus schrieb am Di.,
12. Juni 2018, 15:25:
> On 12.06.2018 14:06, Sven Barth via Lazarus wrote:
> > The dongle code would also be linked if it would be in a dynamic
> > package and Lazarus would support them.
> Sorry, I seem not to be have been clear.
>
> The (potential) pr
On 12.06.2018 14:06, Sven Barth via Lazarus wrote:
The dongle code would also be linked if it would be in a dynamic
package and Lazarus would support them.
Sorry, I seem not to be have been clear.
The (potential) problem I want to provide a solution for is: not to link
the Dongle code in the L
Michael Schnell via Lazarus schrieb am Di.,
12. Juni 2018, 11:48:
> Hence the dongle code will be linked in with the IDE and might (or might
> not) provide problems.
>
The dongle code would also be linked if it would be in a dynamic package
and Lazarus would support them.
The important point is
On 12.06.2018 11:30, Sven Barth via Lazarus wrote:
Only because the code is part of a package that's loaded by the
Delphi IDE does not mean that it also is one in the final Delphi
program. Delphi package distributions more often than not also contain
the DCU for static linking.
Of course you
Michael Schnell via Lazarus schrieb am Di.,
12. Juni 2018, 10:37:
>
> On 11.06.2018 21:03, Bo Berglund via Lazarus wrote:
> > On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus <
> lazarus@lists.lazarus-ide.org> wrote:
> >
> >
> > You want to compile some 3rd party Dongle code in the
On 11.06.2018 21:03, Bo Berglund via Lazarus wrote:
On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus
wrote:
You want to compile some 3rd party Dongle code in the IDE ?
That is more than weired !
Sorry, I don't really know what you mean here...
What is the reason for this com
On Tue, 12 Jun 2018 00:08:42 +0200
Bo Berglund via Lazarus wrote:
>[...]
> >Since your package contains Register procedures it probably has
> >design time stuff.
>
> I don't know what counts as "design time stuff"...
> There is no GUI stuff in the unit at all. But it can be dropped on a
> form
On 06/11/2018 03:03 PM, Bo Berglund via Lazarus wrote:
On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus
wrote:
On 10.06.2018 15:11, Bo Berglund via Lazarus wrote:
... Build IDE: Exit code 2, Errors: 23 ...
You want to compile some 3rd party Dongle code in the IDE ?
That is m
On Mon, 11 Jun 2018 23:17:30 +0200, Mattias Gaertner via Lazarus
wrote:
>On Mon, 11 Jun 2018 21:03:14 +0200
>Bo Berglund via Lazarus wrote:
>
>> On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus
>> wrote:
>>
>> >On 10.06.2018 15:11, Bo Berglund via Lazarus wrote:
>> >> ... Buil
On Mon, 11 Jun 2018 21:03:14 +0200
Bo Berglund via Lazarus wrote:
> On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus
> wrote:
>
> >On 10.06.2018 15:11, Bo Berglund via Lazarus wrote:
> >> ... Build IDE: Exit code 2, Errors: 23 ...
> >
> >You want to compile some 3rd party Don
On Mon, 11 Jun 2018 10:23:44 +0200, Michael Schnell via Lazarus
wrote:
>On 10.06.2018 15:11, Bo Berglund via Lazarus wrote:
>> ... Build IDE: Exit code 2, Errors: 23 ...
>
>You want to compile some 3rd party Dongle code in the IDE ?
>
>That is more than weired !
>
Sorry, I don't really know what
On 10.06.2018 15:11, Bo Berglund via Lazarus wrote:
... Build IDE: Exit code 2, Errors: 23 ...
You want to compile some 3rd party Dongle code in the IDE ?
That is more than weired !
-Michael
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.or
On Sun, 10 Jun 2018 14:59:11 +0200, Mattias Gaertner via Lazarus
wrote:
>Find out the format of your obj file and then find a converter to COFF
>format, which fpc require. Maybe objconv can be used for that. I never
>tried.
Meanwhile I found an old post in the lazarus forum:
https://forum.lazaru
On Sun, 10 Jun 2018 14:15:06 +0200
Bo Berglund via Lazarus wrote:
> On Sun, 10 Jun 2018 12:58:42 +0200, Mattias Gaertner via Lazarus
> wrote:
>
> >Your package must inherit an object search path.
> >
> >Package editor / Options / Package Options / Add path to dependent
> >packages / Object
> >
On Sun, 10 Jun 2018 12:58:42 +0200, Mattias Gaertner via Lazarus
wrote:
>Your package must inherit an object search path.
>
>Package editor / Options / Package Options / Add path to dependent
>packages / Object
>
>Add '$(PkgDir)' without quotes.
>
I did this literally as you wrote. So my Package
On Sun, 10 Jun 2018 12:37:32 +0200
Bo Berglund via Lazarus wrote:
> When converting components to Lazarus (see separate thread) I have
> encountered a problem for a component that interfaces to a software
> protection dongle.
> My component files (pas) need to reference a unit + an obj file from
When converting components to Lazarus (see separate thread) I have
encountered a problem for a component that interfaces to a software
protection dongle.
My component files (pas) need to reference a unit + an obj file from
the dongle maker. In the maker's pas file is this:
IMPLEMENTATION
USES
W
22 matches
Mail list logo
