Hello,
I use Indy 10.2.0.3 in my projects and it works nice, but I have always some problems with package installation. Every time something different, but somehow I'm finally getting rid of errors. However, after latest update to Lazarus 1.8.0 (and also 1.8.2) Indy compilation behaves strangely. I figured out how to make it work, but I don't really like the solution... Here's what I do:
1. Lazarus 1.8.2 32bit clean install (OS: Windows 10 pro 64bit).
2. Indy 10.2.0.3 compilation and installation - compilation successful, IDE is building, Indy components appears on palette.
3. Compilation of my package that uses Indy (let's say MyPackage, and Indy is used by MyModule.pas in MyPackage; Indy is listed in "Required Packages" section of MyPackage) - compilation successful.
4. Compilation of project that uses MyPackage - error: "Cannot find IdTCPServer used by MyModule, incompatible ppu=(path to ppu in Indy directory), package indylaz". Strange, MyModule was alredy successfully compiled in step 4.
5. After trying different solutions I added path to fpc directory in Indy files to "Other unit files" in MyPackage settings, then recompiled Indy package and MyPackage (both compiled successful). Now project using MyPackage runs without problems, but Indy .ppu files are duplicated - they are both in Indy directory and MyPackage directory. Which I guess is not good.
6. Now I'm trying to install different package (unrelated to Indy) and it turns out that IDE is failing to rebuild with error: "IdAboutVCL.pas(78,12) Fatal: Cannot find IdAboutVCL used by IdAbout, incompatible ppu=(path to ppu in Indy directory), package indylaz". Besides that, there are warnings about duplicated .ppu files.
7. I delete Indy .ppu files from MyPackage directory, remove path to Indy from "Other unit files" in MyPackage, recompile MyPackage (successful). Now I'm back in step 4 - I'm able to rebuild IDE, but projects using MyPackage aren't working anymore. So after working with IDE I go to step 5 to fix it by making mess with .ppu files again.
Problem occures also in projects that directly use Indy package - adding path fixes compilation error. Other dependencies between packages works correctly, just by adding requirement, with no need to add paths to another package files.
Anybody has idea what is happening here? Is there a way to permanently fix both of these errors?