How to compile whole delphi virtual tree view in lazarus in one compile?

[Sanem]

Hi everyone, I am trying to compile the Delphi version of virtual tree view (https://github.com/JAM-Software/Virtual-TreeView) in Lazarus trunc  2.3.0 FPC 3.3.1, I was wondering if I could compile the whole package in one compile and get all the errors and incompatibilities in one pass? to be able to decide if this is even possible or not.

Any thoughts on this matter or porting the Delphi virtual tree view to Lazarus in general would be a lot help and appreciated.


Thanks for your response in advance
Regards

[wp]

VTV already has been ported to Lazarus (https://github.com/blikblum/VirtualTreeView-Lazarus), however, it is not up-to-date with the latest JAM-Software version. There is even a version incorporated in Lazarus. In all my applications using VTV I am happy with these out-dated versions.

Be prepared for a lot of work if you'd attempt to port the latest JAM-Software version. Maybe you should contact blikblum (Luiz Americo) who did the Lazarus port to get a realistic estimate of the issues that he had.

[Sanem]

Thank you very much, I am just testing and estimating the issues.
I used https://wiki.freepascal.org/lazbuild to compile the package all together, bu I only got the same errors IDE gives which is only 1 or 2 in each step.
Any other thoughts?

[Sanem]

VTV already has been ported to Lazarus (https://github.com/blikblum/VirtualTreeView-Lazarus), however, it is not up-to-date with the latest JAM-Software version. There is even a version incorporated in Lazarus. In all my applications using VTV I am happy with these out-dated versions.

Be prepared for a lot of work if you'd attempt to port the latest JAM-Software version. Maybe you should contact blikblum (Luiz Americo) who did the Lazarus port to get a realistic estimate of the issues that he had.

Thank you, I'm trying to use the delphi version for the performance improvements, and I am aware of other ported lazarus versions.

[El Salvador]

Given the difference between the two forks (and the refactoring work done on the fork for Delphi, splitting a piece of code into smaller units), perhaps you should start from the Delphi fork and porting the blikblum changes in this fork, and at the same time resolve all compilation errors. Once done, start fixing runtime bugs on Windows (and so on on the other os / widget sets). This work is huge for one person (kudos for blikblum)!

[Sanem]

Given the difference between the two forks (and the refactoring work done on the fork for Delphi, splitting a piece of code into smaller units), perhaps you should start from the Delphi fork and porting the blikblum changes in this fork, and at the same time resolve all compilation errors. Once done, start fixing runtime bugs on Windows (and so on on the other os / widget sets). This work is huge for one person (kudos for blikblum)!

Thanks for your response but I knew the stuff you mentioned and my question was about something else.

Regards