Recompile FPC Package

[paweld]

@TRon: The only change I had to make to get the current fppdf to compile without problems was to remove the parameters at the GetLocalTimeOffset function (fppdf.pas, line 1390).
Just an important thing - I downloaded the fcl-pdf sources from the FPC 3.2-fixes version, which is consistent with the trunk version (it just doesn't have the DOTTEDUNITS parts)

[TRon]

@paweld:
Indeed you are correct. I did not realize that most of the changes in trunk also found its way to 322 fixes. For Linux it (also) does not compile because of missing identifier FcConfigGetFilename but that wasn't TS' target.

There are some additional changes in trunk though that renders it incompatible with 3.2.2.

However, imho the main issue is that TS still did not mention the current version of the FPC compiler in use and with what version of the fcl-pdf package it should be updated. For all we know it is 3.0.4 wanting to update the pdf package to/with trunk version as we do not know what fixes TS is interested in and/or are necessary for TS' project.

Thank you for testing/feedback paweld. Seems like a misunderstanding between versions (hence why it is important for TS to enlighten us on that matter as well).

[paweld]

I'm still attaching an example that uses page links (available in fixes/trunk version) - compiled using FPC 3.2.2

[TRon]

yes i work with other people on this Project and they do not want to update Lazarus/FPC yet. So i cant work with them when they have an older version of Lazarus, because they can't open/compile my work.

In light of recent findings by paweld I fail to see why making the situation more difficult then it would have to be justifies any reason to not update.

There is actually no need to update anything at all other than installing FPC 3.2.2 fixes (still under the assumption you and your teammates are running 3.2.2), point your existing Lazarus to the new fixes compiler and rebuild Lazarus (a single button action).

I can respect the need/requirement to stay at a certain version/revision of software but the release schedule of the compiler is already as dissatisfying as it can be (no offense).

i guess the best way for me now is to leave it for now since i can't just recompile the single package due to dependencies. I will mark this section in the project as unfinished and come back later when all of my coworkers agree to update Lazarus.

Respect for your decision but as I wrote above there is no need to update Lazarus.

i do not have any knowledge about fpc so thats one more reason to stop here and come back later when i have a clean and safe Updated version. Maybe this thread could help someone else in a similar situation.

Fixes is as clean and safe as it can get.... even safer than keep running FPC 3.2.2 release version (still the same assumption that your team is running 3.2.2)

The only thing that we can't answer is what version of the compiler your team is currently using and what fixes you need for the fcl-pdf package in order for you to be able to continue your project 

edit: forgot to mention that you can always go paweld/wp route if that works for you and your teammates.