Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: buildroot@busybox.net
Subject: [Buildroot] Naming of libraries.
Date: Sat, 4 Nov 2006 18:48:41 -0500	[thread overview]
Message-ID: <200611041848.41847.rob@landley.net> (raw)
In-Reply-To: <20061103081507.GA9631@zelow.no>

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

  reply	other threads:[~2006-11-04 23:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  8:15 [Buildroot] Naming of libraries Thomas Lundquist
2006-11-04 23:48 ` Rob Landley [this message]
2006-11-05  0:10   ` don
2006-11-05  8:27   ` Thomas Lundquist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200611041848.41847.rob@landley.net \
    --to=rob@landley.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox