#1 Re: mORMot 2 » How can I check framework version within a compiler directive » 2024-10-16 20:27:42

Lazarus package is still on 2.0.1 on stable 2.3:
https://prnt.sc/jqwVHOOTEixj

You should consider updating this number, so any other packages who depends on mORMot2 can make a better version-aware depedancy with it, for example:
https://prnt.sc/QRDDnOncArm4

#2 Re: mORMot 2 » How can I check framework version within a compiler directive » 2024-10-16 08:32:39

Thanks ab, those directives will solve the issue and since it'll be a new release I'll aim the compatibility into it

Also the .lpk should replicate the version info, its still 2.0.1

#3 mORMot 2 » How can I check framework version within a compiler directive » 2024-10-16 07:17:17

Mobius1
Replies: 3

Hi, I need to reliably check SYNOPSE_FRAMEWORK_VERSION between 2.2 stable and 2.2 main to adjust a code, I tried doing:
{$IF StrToIntDef(Copy(SYNOPSE_FRAMEWORK_VERSION, Length(SYNOPSE_FRAMEWORK_VERSION) - 4, 4), 0) >= 8236}
but it didn't work... I'm on lazarus 3.7/FPC 3.2.3 atm but the code should be compatible with Delphi as well.

Does anyone have an idea on how I should do this check? Thanks in advance

#4 mORMot 2 » SSH Support » 2023-11-19 23:44:15

Mobius1
Replies: 1

Hi, does mORMot2 support SSH connection? IF yes, is there any example anywhere? Thanks in advance

#5 Re: mORMot 2 » [Fixed] Trying to create a component that uses mORMot2 » 2023-09-08 21:28:23

Apparently everything is working as intended, if I stumble upon some other issue I'll open another topic, thanks for the workaround to bypass Delphi's bug.

#6 Re: mORMot 2 » [Fixed] Trying to create a component that uses mORMot2 » 2023-08-17 22:24:19

Got a few other definition errors on mormot.crypt.core.pas, will do the same {$IFDEF} directives you made on the other units and will send a PR with the adjustments, only 2 types were not treated.

#7 Re: mORMot 2 » [Fixed] Trying to create a component that uses mORMot2 » 2023-08-17 19:40:18

Thanks! I will do some testing in a bit and will report the findings.

#8 Re: mORMot 2 » [Fixed] Trying to create a component that uses mORMot2 » 2023-08-17 08:30:51

11.3 Alexandria, but the same thing happens on 10.3.3 Rio, tested on this other version that I have installed here.

In runtime it compiles no problem, the .dpk throws the error. I want to create a design-time component using mORMot2, so for that It needs to compile in design-time as well... Asked on delphi global community about the issue but so far no one was able to help with the matter.

On lazarus it work like a charm, I have the component made beautifully, but on Delphi...

#9 mORMot 2 » [Fixed] Trying to create a component that uses mORMot2 » 2023-08-16 21:16:52

Mobius1
Replies: 9

Hi,
I'm having issues trying to compile a delphi package that uses some units from mORMot2. I'm creating a component that is based on the suite but Delphi doesn't wanna compile it, it doesn't accept type = object for some reason. Detailed issue below:

I'm trying to create a package that creates a design-time component for mORMot2. Problem is, delphi keeps complaining about a type = object declaration on the code as shown in the image:
image.png

going through docwiki, I found out this segment that states object types are there only for backwards compatibility and shouldn't be used.
https://docwiki.embarcadero.com/RADStud … s_(Delphi)
image.png

In runtime the component works, it compiles and doesn't throw any errors, but if I try to create a .dpk to use the component in design time, then the package can't compile due to these errors, any Ideas on what I should do?

Board footer

Powered by FluxBB