package for Lazarus fpc 3.2+

[alexrayne]

There provided fresh run-time FPC Lazarus package, that well builds on win10x64 with lazarus 2.3 fpc 3.2.2

• FPC package and code resides in fpc/ folder

• starts asm code extracting on -> machine-dependent sources, with FPC-stylec directory structure: x86/ and x86_64/ dirs are CPU-targets

• problems: FPC planed lambdas on ver3.3. So TDECProgressEvent still maybe only procedure

[MHumm]

Thanks for this pull request! I try to have a look at the code soon, but:

1. Can you please change it so that this is for development branch instead of master branch? I want to have such contributions in development branch first.
2. I'm not 100% sure yet what the benefit will be (maybe when I look at the code): it creates packages for DEC so it can be used as package?
3. Be aware please that I don't use FPC and while I value and like FPC compatibility, I cannot test FPC stuff (ok, I could install it and test on Windows at least, but my time is unfortunately limited as well). So it would be nice if somebody could change such FPC related stuff now and then to make sure we don't break any of it when further working on DEC.

[alexrayne]

1. As i unwerstand git, there no matter where i base PR, it's is your desigin - where to merge it. Should i still rebase this PR on to develop?

2. Yep, this is runtime package for lazarus IDE. old lazarus package source/DEC60Lazarus.lpk provided for fpc2 - that is ancient legacy, totaly incompatible with modern Deplhi, and even modern FPC

3. as for testing, FPC provides wide range of OS and CPU targets. that is huge work to test them all. imho, you beter rely this work on users )/ You better test Deplhi packages, since i have no Delphi, and can`t test Embarcadero packages

[MHumm]

The only things I don't really understand yet are these x86 and x64 includes with the swap routines. It would be good to have unit tests for those as well. Can you add some?

[alexrayne]

there alredy test project in repo, that imports and builds well with lazarus. I`ve run it on x86_64, so looks it tested