[ Charset ISO-8859-1 unsupported, converting... ]
> On 4/5/06, Panagiotis Sidiropoulos
> > - Is it smart to link all libs used into executable?
>
> If they are small in size and do some specific work for you and the
> lib has no external dependencies and the copyright is ok, it is easier
> to link this lib statically in your executable.
> More libs, bigger executable.
But keep in mind that
1) "shared libs" + "binary that uses shared libs" > "static binary"
IOW, to lower the overall size, you must be sure that the binary is reused.
2) Static binaries are way easier to deploy.
> Static linking links all code from the lib, not only functions that
> you use IIRC.
This is true for older GCC's, and afaik newer ones without proper arguments,
but FPC supports smartlinking.
> Dynamic linking is used more frequently.
Only for binaries that are delivered/packaged with the system. So in general
it is wiser to build shared when building for a specific distro/version, and
static else.
> My advice is to loose some more time and make you app use dynamic linking.
> Prepare a distribution package for your app with all dependencies.
> E.g. .deb for Debian/Ubuntu, .rpm for SuSE/Fedora. This will solve
> conflicts with dependencies automatically when the package is
> installed.
Yeah, it won't install because of the dependancy. But if this is a
solution!??!
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
