How to make units/libs available to all projects like in Delphi?

[snorkel]

Hi,
Currently I am using libs like Synapse,SQLite Wrapper and SuperObject, none of these are visible components and for each new project I have to add them to the project options/Compiler Options/Other Unit Files

Is there a way to have a global Paths like in Delphi that applies to all existing and future projects?  I have only recently started using Lazarus instead of Delphi for a lot of things and love but I don't know everything about it yet :-(

Thanks,

Snorkel

[Bart]

Assuming the relative path to the libs are the same for all your project, you can go to project options -> paths, fill in the correct paths, then check the checkbox "Use these compiler options as default for newprojects" and save.

Now all your new projects have the correct paths.

All my Lazarus projects reside in a subfolder of /path/to/lazdev/, so this works perfectly for me on all my 2 Windows and 1 Linux setup.

If the relative paths for new projects isn't the same, you can include the paths as absolute paths.
The disadvantage is that when compiling the project on a different machine or OS, the absolute paths are probably wrong and need correcting.


Bart

[marcov]

I haven't tried it, but the package system of Lazarus is potentially better than Delphi here:

1) Stuff all your general units into a non visual package
2) compile it and install it into Lazarus.
3) let your projects depend on that package.

This has several advantages:
1) the dependency in the project is on the package, not on an absolute path.
2) it's only one dependency on the package, not multiple paths.

You can even add a version number to the (super) package name, and e.g. upgrade
the version of the superpackage used in a project by simply deleting the old (e.g. superpackage102)
dependency and adding the new one. Being able to have multiple sets of these libraries in one Lazarus installation.

[Leledumbo]

Put it in fpc.cfg.

[JD]

Put it in fpc.cfg.

Then one has to update fpc.cfg after every Lazarus upgrade because the old customized fpc.cfg is likely to be overwritten after the upgrade.

[Bart]

Put it in fpc.cfg.

IIRC compiling works, but code-tools cannot find the units...?

Bart

[Leledumbo]

IIRC compiling works, but code-tools cannot find the units...?

Yes, since codetools needs to find the source code. If it's the intention I think the only easy way is to create a project template with the paths (or better, create a package and add it to the project dependency).