Indy, can't find unit's on compiling the project, not the package. lazarus / 38-Networking and Web Programming ---------------------------------------------------------------------- everton · 2012-01-28 18:14 On compiling the package they do. But when i compile a project that contains a Indy component they say that can't find the units. I've tried to go in the project inspector and removed and include again the indylaz but doesn't work. ---------------------------------------------------------------------- everton · 2012-02-07 10:32 Well, i`ve managed to compile putting the indy ../fpc directory in the search path to compile of the project. Isn`t the better solution, but worked, at least for now. ---------------------------------------------------------------------- JD · 2012-02-07 11:16 Quote from: everton on February 07, 2012, 11:32:25 amWell, i`ve managed to compile putting the indy ../fpc directory in the search path to compile of the project. Isn`t the better solution, but worked, at least for now. AFAIK that is the only way I've managed to compile Indy projects on Windows or on Linux. I wonder if there's a better way too. ---------------------------------------------------------------------- everton · 2012-02-07 15:28 The compiler isn`t been able to find the directory ../fpc that is specified on package compiler options. That`s the trouble. Maybe a bug? ---------------------------------------------------------------------- JD · 2012-02-07 15:53 Quote from: everton on February 07, 2012, 04:28:50 pmThe compiler isn`t been able to find the directory ../fpc that is specified on package compiler options. That`s the trouble. Maybe a bug? All my Indy files are in the same folder. See the attached text file for the contents of my Indy10 folder. In addition, in the Unit field under the package options dialog, I typed the following: $(PkgOutDir);$(LazarusDir)\components_extra\Indy10_4667 In the Paths part of the package's Compiler Options, I have the following: lib\$(TargetCPU)-$(TargetOS) I then add the $(LazarusDir)\components_extra\Indy10_4667 to all my projects that use Indy10. I've been able to compile my Indy10 projects without problems in Windows and Linux using this method. I've not tried it in MacOS yet though. JD ---------------------------------------------------------------------- everton · 2012-02-07 16:53 Yes, inserting the path on the project compiler path it compiles. But, isn't supposed to compile with the path on the package compiler path? ---------------------------------------------------------------------- JD · 2012-02-07 20:19 Quote from: everton on February 07, 2012, 05:53:55 pmBut, isn't supposed to compile with the path on the package compiler path? That's what I thought but it didn't seem to work that way. ---------------------------------------------------------------------- everton · 2012-02-08 12:57 So, is a bug. At least, i guess. The problem, is to test that bug, when it happens, is in all packages that happens or is only in some cases, that`s one question. By now, i can`t do this tests, if anyone else have interests in the case... please, let`s do. ---------------------------------------------------------------------- JD · 2012-02-08 14:43 Quote from: everton on February 08, 2012, 01:57:03 pmSo, is a bug. At least, i guess. The problem, is to test that bug, when it happens, is in all packages that happens or is only in some cases, that`s one question. By now, i can`t do this tests, if anyone else have interests in the case... please, let`s do. You may need to report this on the Indy forum at http://forums2.atozed.com/viewforum.php?f=6 ---------------------------------------------------------------------- everton · 2012-02-09 09:57 Yeah, but i think is a fpc issue. ---------------------------------------------------------------------- JD · 2012-02-09 12:26 Quote from: everton on February 09, 2012, 10:57:27 amYeah, but i think is a fpc issue. I'm not so sure because I also had huge problems getting it to compile in Delphi. There the problem was one had to completely uninstall the older version of Indy from the system before installing an updated version. And that is very, very difficult to do. The Lazarus installation was a walk in the park for me compared to that. As a matter of fact, I have 3 Indy versions in my Lazarus installations. I only need to change file paths to select a particular version when I'm compiling a project. So advantage Lazarus! ---------------------------------------------------------------------- everton · 2012-02-09 17:16 Vincent Snijder (manager) in the BugTracker has spoken: "This is an issue with the Indy makefiles. Report them at the Indy makefile maintainer." But I have no idea how to report that, i know so little about makefiles... ---------------------------------------------------------------------- everton · 2012-02-19 12:39 I tried to use the "Create Makefile" in the button "More" of the package but didn`t work too. Wasn`t supposed to recreate the makefiles with the config of the package? Or there's anything more about the makefiles that i`m not aware. ---------------------------------------------------------------------- everton · 2012-02-19 13:00 I`m considering to port to synapse my projects it seems to be more adapted to the lazarus/fpc environment. ---------------------------------------------------------------------- everton · 2012-02-20 10:26 Synapse has his lacks on support too, by now i'll stay on Indy since is already done in. ---------------------------------------------------------------------- JD · 2012-02-24 14:32 Ok, I'm back.  I still don't understand why you need the Indy Makefiles so much. I've never touched them and the package still works fine. ---------------------------------------------------------------------- marcov · 2012-02-24 20:13 Quote from: JD on February 24, 2012, 03:32:32 pmOk, I'm back.  I still don't understand why you need the Indy Makefiles so much. I've never touched them and the package still works fine. The makefiles also run fine iirc. Just kill all redundant copies of the .inc files or compile with -Ur. ---------------------------------------------------------------------- leongcheokteng · 2013-02-20 03:39 I am a new user and seemed to find a solution: 1) Open loaded package; choose 'indy 10' and open it; 2) Click button Options; 3) In Package Options-> Usage->Include,  type the path ../fpc (or full path in my case); 4) Click button Compile; 5) Rebuild your project to check whether it works. Note: 1) In the way, no need to add path your each project you use Indy. 2) It is NO USE to type the path in the compiler options. 3) Hope this will help other new users. Tell me if I am wrong. ---------------------------------------------------------------------- coliv_aja · 2014-02-20 14:38 I just come to this after year not using Lazarus and Indy. And i just realize Indy package marked as "Designtime" only on IDE integration  . Just change it to "Designtime and runtime" then everything will work  fine. Step by step for new user: 1. Copy folder Core, Protocols, System and indylaz.lpk to your desired place. 2. Open indylaz.lpk 3. Options > Package Options > IDE integration > Choose "Designtime and runtime" 4. Options > Compiler options > Paths > Other unit files add "Core;Protocols;System" 4. Compile 2 time. 5. Use >> Install > Rebuild IDE