Other unit file paths in compiler options issue lazarus / 8-Other ---------------------------------------------------------------------- JimBodkins · 2006-09-22 21:50 I have a project (project1) that uses two additional units - call them libunit and myunit. Uses ...... , libunit, myunit; project1 can find both after I set the  additional unit path to point to their folders. Myunit also uses libunit - it works fine in tests (a project in the myunit folder to test classes in myunit). libunit is located. in project1, libunit is located, myunit is located but myunit FAILS to locate libunit even though project1 (the outer entity in this case) has already located it. It appears that the other unit paths arent being used recursively. (Guessing) This is a deal breaker for us as we must be able to do this (or something like this). We have built and will build more classes that use the same librarires that are used by the main projects. Am I missing something or is this a bug - not using the paths recursively as additional units are used. Thanks Jim ---------------------------------------------------------------------- Onjahyr-BR · 2006-09-22 23:53 Which is the question? Code: [Select] unit myunit; {$mode objfpc}{$H+} interface uses   Classes, SysUtils, LResources, Forms, Controls, Graphics, Dialogs; type   TForm1 = class(TForm)   private     { private declarations }   public     { public declarations }   end; var   Form1: TForm1; implementation uses libunit    // <--- initialization   {$I unit1.lrs} end. .rda. ---------------------------------------------------------------------- JimBodkins · 2006-09-23 02:27 Thanks for the reply. That approach produces graphics unit not found. (ie, the paths appear to be fubared at that point) I should have mentioned that there are three folders involved here, the project folder, and two separate folders each of which contain units that are 'used' - one is a low level 'library' of database functions and the other contains class definitions that implement applications that use the database functions. (The additional unit path contains two entries - one to each) Another thing that happens is - even though the project only uses unit1 - a spurious unit2 is included from the folder that contains myunit. (Which of course errors). That unit2 is part of a project that I use to test myunit and happens to be in the same folder. I tried buying a book on pascal from  the local barnes and nobel but they didnt carry any ... not one ... on the grounds that there was no market for it. It appears that the 'pathing' isnt quite right. (I think)