How to edit Path-Templates lazarus / 11-Options ---------------------------------------------------------------------- DimProfi · 2013-04-08 00:04 There is a dialog to edit the pathes to a units (-Fu) And at the bottom are Path-Templates like: $(LazarusDir)\lcl\units\$(TargetCPU)-$(TargetOS) $(LazarusDir)\lcl\units\$(TargetCPU)-$(TargetOS)\$(LCLWidgetType) $(LazarusDir)\components\codetools\units\$(TargetCPU)-$(TargetOS) ... How can I add some own pathes to this list? I have units which will be used in every project and its no fun to insert the pathes to a project every time  So it would be much faster with path templates. ---------------------------------------------------------------------- Martin_fr · 2013-04-08 00:29 You can add them as to project options and save as default. But you better group your units into a package (just create a new empty package in a new folder, copy units into that folder, and in package: add files) Then add that package to each project ---------------------------------------------------------------------- DimProfi · 2013-04-08 00:56 QuoteYou can add them as to project options and save as default. The projects are created from different Lazarus templates. So i need some of them  QuoteBut you better group your units into a package (just create a new empty package in a new folder, copy units into that folder, and in package: add files) Then add that package to each project There are different pathes, which i need, and some new comming additionally from time to time ---------------------------------------------------------------------- Martin_fr · 2013-04-08 02:31 Well, I do recommend to find a way to use packages. Experience (from what I read, what other people went through) shows that all else, will eventually get you into trouble. But you can add the pathes in the fpc.cfg (same dir as fpc.exe) That file is global, and pathes (or other settings) in there will be used by all projects ---------------------------------------------------------------------- DimProfi · 2013-04-08 02:37 Packages are not good, because I'm compiling sometimes without Lazarus directly with FPC. May be I will use a fpc.cfg solution or investigate Lazarus code, to find a source of path templates ---------------------------------------------------------------------- BigChimp · 2013-04-08 04:57 Quote from: dimprofi on April 08, 2013, 04:37:46 amPackages are not good, because I'm compiling sometimes without Lazarus directly with FPC. You can also use lazbuild to build Lazarus projects/packages from the command line. Perhaps that could be useful? ---------------------------------------------------------------------- Paul_ · 2016-04-14 13:46 It seems like $(TargetCPU)-$(TargetOS) doesn't work  in FPC.CFG. There is different tag? Quote-FuC:\Development\lib\zlib\$(TargetCPU)-$(TargetOS) Unfortunately, nothing found in documentation about it. ---------------------------------------------------------------------- avra · 2016-04-15 10:31 Quote from: DimProfi on April 08, 2013, 02:04:14 amI have units which will be used in every project and its no fun to insert the pathes to a project every timeAlternatively you can use relative and absolute paths for your units when mentioning them in uses clause. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i uses  MyLibUnit1 in '..\MyLib\MyLibUnit1.pas',      // relative path  MyLibUnit2 in 'C:\Prg\MyLib\MyLibUnit2.pas';  // absolute path