[fpc-pascal] A linking error when compiling with FPC 2.4.4

Felipe Monteiro de Carvalho felipemonteiro.carvalho at gmail.com
Mon Oct 31 12:39:15 CET 2011

On Mon, Oct 31, 2011 at 12:10 PM, Michael Van Canneyt
<michael at freepascal.org> wrote:
> This would add a whole list of unwanted dependencies to e.g. lazarus since
> it installs support for many databases by default. It loads the needed
> libraries on-demand; if someone needs it, he/she can install the needed
> libraries with the package-manager.

Are you sure? I think it works differently. Lazarus bigide includes
design-time support only for those datasets without any external
dependencies. Other datasets have to be installed by the user, or used
without design support (like I do). And when they are installed the
IDE gains a static dependency on them from what I remember, so, for
example, you need to copy DLLs to the Lazarus directory if you install
such packages. I think that releases use bigide (not sure since I'm
always in trunk, however)

But indeed it would cause problems for people installing the debs for
sure, because there is a truck load of deb files, so selecting which
ones you want/need is a long and boring task, so I usually just try to
install *.deb, which would unwantedly install a truckload of databases
now =D

Another big problem is the more dependencies you add, the more
distribution specific the packages get, so if packages are named
differently in Ubuntu vs Debian vs other deb-based you get a package
which does not install everywhere.

The RPM has the inverse problem. It is 1 with everything, so if
theorically you added dependencies there too you would have immense
dependencies for FPC, which would surely make the package impossible
to install in most systems. Actually it is already impossible to
install FPC RPMs in PCLinuxOS and other systems because of the
text-mode IDE dependencies.

Felipe Monteiro de Carvalho

More information about the fpc-pascal mailing list