[Buildroot] Naming of libraries.

[Buildroot] Naming of libraries.

[Thomas Lundquist]

I am making packages for qwt and gd and I ended up with pondering about
what to call the package.

It does look like all libraries are prefixed with "lib" but most of them
have lib prefixed in their name anyway.

Couldn't find anything in the docs either.

So, should all libraries be prefixed with "lib"?


Thomas.

[Buildroot] Naming of libraries.

[Rob Landley]

On Friday 03 November 2006 3:15 am, Thomas Lundquist wrote:
> 
> I am making packages for qwt and gd and I ended up with pondering about
> what to call the package.
> 
> It does look like all libraries are prefixed with "lib" but most of them
> have lib prefixed in their name anyway.
> 
> Couldn't find anything in the docs either.
> 
> So, should all libraries be prefixed with "lib"?

When you tell gcc "gcc -lcurses" it looks for libcurses in the library search 
path.  Because gcc looks for things starting with "lib", people add that to 
their library names to use gcc.  (Everybody agrees ".exe" is stupid for 
executables, and libraries already have .a or .so anyway, but this is the FSF 
we're talking about.  Making sense was never a strong suit with them.)

(And yes, I honestly think they believe "-liberty" as a command line option is 
funny or something, hence libiberty.a)

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery

[Buildroot] Naming of libraries.

[don]

On Sat, Nov 04, 2006 at 06:48:41PM -0500, Rob Landley wrote:
> When you tell gcc "gcc -lcurses" it looks for libcurses in the library search 
> path.  Because gcc looks for things starting with "lib", people add that to 
> their library names to use gcc.  (Everybody agrees ".exe" is stupid for 
> executables, and libraries already have .a or .so anyway, but this is the FSF 
> we're talking about.  Making sense was never a strong suit with them.)

This convention was in Unix long before the FSF came along, don't blame
them.

Don Reid

[Buildroot] Naming of libraries.

[Thomas Lundquist]

On Sat, Nov 04, 2006 at 06:48:41PM -0500, Rob Landley wrote:
> 
> When you tell gcc "gcc -lcurses" it looks for libcurses in the library search 
> path.  Because gcc looks for things starting with "lib", people add that to 
> their library names to use gcc.  (Everybody agrees ".exe" is stupid for 
> executables, and libraries already have .a or .so anyway, but this is the FSF 
> we're talking about.  Making sense was never a strong suit with them.)

hehe, ok.

the question was more of a naming convention issue in buildroot but I
guess it's just like that for other purposes.

(slang and ncurses are not prefixed with lib, so I guess it's no real
issue.)

> (And yes, I honestly think they believe "-liberty" as a command line option is 
> funny or something, hence libiberty.a)

but it is :=)


Thomas.