[Solved] Installing fpreport? lazarus / 31-LCL ---------------------------------------------------------------------- mtrsoft · 2019-02-01 19:06 :)I'm using a Win7/32 system and Lazarus v1.8.4 or v2.0.0 RC3 and am not able to install fpreport. When attempting to install the lclfpreport package I get the error messages "Compile package lclfpreport 0.0: Exit code 1, Errors: 1 cfgfpreportimageexport.pp(24,42) Fatal: cannot find fpreport used by cfgfpreportimageexport of package lclfpreport." Here's what I did: 1. Downloaded fpreport from .../svn/trunk/componennts/fpreport/    (Most of the files had a date of 2017-8-20.)     2. Copied all of the files and directories to the directory: C:\lazarus\components\fpreport. 3. Used the menu items "Packages > Open Package file" to open the file "lclfpreport.lpk". 4. Compiled the package. -- The result was the error mentioned above. The question is: What am I missing? TIA. A small update: I have also downloaded the files from .../svn/lazarus/branches/fixes_2_0/components and got the same result. ---------------------------------------------------------------------- laz_frank · 2019-02-04 13:09 Try Lazarus fixes 2.0 and FPC fixes 3.2.0 as fpReport does not run with current stable releases. http://wiki.lazarus.freepascal.org/FPReport_FAQ ---------------------------------------------------------------------- valdir.marcos · 2019-02-04 17:39 Quote from: mtrsoft on February 01, 2019, 08:06:36 pmI'm using a Win7/32 system and Lazarus v1.8.4 or v2.0.0 RC3 and am not able to install fpreport. When attempting to install the lclfpreport package I get the error messages "Compile package lclfpreport 0.0: Exit code 1, Errors: 1 cfgfpreportimageexport.pp(24,42) Fatal: cannot find fpreport used by cfgfpreportimageexport of package lclfpreport." Here's what I did: 1. Downloaded fpreport from .../svn/trunk/componennts/fpreport/    (Most of the files had a date of 2017-8-20.)     2. Copied all of the files and directories to the directory: C:\lazarus\components\fpreport. 3. Used the menu items "Packages > Open Package file" to open the file "lclfpreport.lpk". 4. Compiled the package. -- The result was the error mentioned above. The question is: What am I missing? TIA. A small update: I have also downloaded the files from .../svn/lazarus/branches/fixes_2_0/components and got the same result.Temporary easier and complete solution: Use FPCUPdeluxe to get Lazarus 2.0.0 RC 3 + fixes_2_0 and FPC 3.2 beta + fixes_3_2: fpcupdeluxe - Lazarus wiki http://wiki.lazarus.freepascal.org/fpcupdeluxe Then follow this information: FPC 3.2.x series branched, trunk update to 3.3.1 http://forum.lazarus.freepascal.org/index.php/topic,42265.msg308381.ht ml#msg308381 There is already an open bug report about it: 0034887: Lazarus 2 RC 3 + FPC 3.2.0 beta - after fpReport package install Lazarus stops working missing libraries https://bugs.freepascal.org/view.php?id=34887 ---------------------------------------------------------------------- JD · 2019-02-04 19:45 @valdir.marcos Thank you sooo much. It works. ---------------------------------------------------------------------- mtrsoft · 2019-02-06 02:32 @valdir.marcos, Thank you. Fpcupdeluxe is greatly simplifying things for me. Using it I have managed to install Fpc v3.3.1 and Lazarus v2.1.0. Now my main problem is that I don't know where to put the freetype-6.dll and zlib1.dll files. One comment about fpcupdeluxe -- It kept stalling whenever it downloaded a utility file (such as, cp.exe, cpp.exe, gbd.exe, zip.exe and many others). I had to stop fpcupdelux, using the Task Manager, and run it again. Once all of the utilities were downloaded to the c:\fpcupdeluxe\fpcudeluxe\fpcbootstrap directory there was no problem. ---------------------------------------------------------------------- JD · 2019-02-06 18:23 Quote from: mtrsoft on February 06, 2019, 03:32:02 am Now my main problem is that I don't know where to put the freetype-6.dll and zlib1.dll files. I put it in the same directory as Lazarus.exe ---------------------------------------------------------------------- mtrsoft · 2019-02-06 22:09 Thank you JD. It's now all working.