compile path/missing unit problems lazarus / 1-Linux ---------------------------------------------------------------------- mbohn · 2009-12-16 19:44 fpc 2.5.1 Lazarus 0.9.29 Ubuntu 9.10 When I try to compile my app I get missing-unit errors.  I fixed the first one by manually locating FileUtil and adding it to my compile path.  Now, I get "Can't find unit WEReferences used by LCLProc."  I'm assuming this could go on ad infinitum. Is there a problem with my fpc/Lazarus install?  I did it by installing CodeTyphon?  Is that a mistake? Is there an easy way to set up all the compiler paths? Thanks. ---------------------------------------------------------------------- Marc · 2009-12-16 23:31 Quote from: mbohn on December 16, 2009, 08:44:05 pmfpc 2.5.1 Lazarus 0.9.29 Ubuntu 9.10 When I try to compile my app I get missing-unit errors.  I fixed the first one by manually locating FileUtil and adding it to my compile path.  You should never add the LCL sources to your compile path. Only point to the dir where the compiled units of the LCL are. Normally the IDE will do this for you if you add a depencency to the LCL to your project. QuoteNow, I get "Can't find unit WEReferences used by LCLProc."  I'm assuming this could go on ad infinitum. Yes, that was to be expected. QuoteIs there a problem with my fpc/Lazarus install?  I did it by installing CodeTyphon?  Is that a mistake? Is there an easy way to set up all the compiler paths? I don't know codetyphoon, but I thought it set this up for you. For a normal project, you don't have to specify any special dir. The only thing you have to configure the first time in the environment options are the path to the compiler, the lazarus sources and the fpc sources. IIRC codetyphoon does that for you. ---------------------------------------------------------------------- mbohn · 2009-12-17 01:32 QuoteYou should never add the LCL sources to your compile path. Only point to the dir where the compiled units of the LCL are. Normally the IDE will do this for you if you add a depencency to the LCL to your project. By dependency you mean putting a unit in the uses clause or just calling a function that is in a library unit? QuoteYes, that was to be expected. Why, and what do I do about it? QuoteI don't know codetyphoon, but I thought it set this up for you. For a normal project, you don't have to specify any special dir. The only thing you have to configure the first time in the environment options are the path to the compiler, the lazarus sources and the fpc sources. IIRC codetyphoon does that for you. I've added 2 screen shots, one for my Project Compiler Options and the other for Environment | Files.  Do you see anything wrong with the way this was set up at install? Thanks! ---------------------------------------------------------------------- Marc · 2009-12-17 09:57 I meant, adding it to the "other unit files" option of your project options. From your screenshot I see you didn't, so that's good. You mentioned that you added something to your file path, where did you do that ? ---------------------------------------------------------------------- mbohn · 2009-12-17 13:27 I removed those after reading your first response, but I can reconstruct for you what I did: First time I tried to compile my app I get the following compile error: "Identifier not found UTF8ToSys" which is in the FileUtil unit. I search for that unit and find the .pas file in /usr/lib/lazarus/lcl. I add that path to Project Compiler Options, I think in the "Other Unit Files" section. But more to the point, are the screen shots correct as you see them above? If so, how do I fix the "Identifier not found UTF8ToSys" problem?  And will that fix other missing unit errors? Thanks. ---------------------------------------------------------------------- Marc · 2009-12-17 19:12 Your screenshots are ok. Don't change it. Did you add FileUtil to the uses clause of the unit where you want to use UTF8ToSys ? ---------------------------------------------------------------------- mbohn · 2009-12-17 19:34 Yes, and that has now gotten me past that problem.  Hopefully, the others will go away too. Thanks much for your help.