From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] Naming of libraries.
Date: Sun, 5 Nov 2006 09:27:26 +0100 [thread overview]
Message-ID: <20061105082726.GA1158@zelow.no> (raw)
In-Reply-To: <200611041848.41847.rob@landley.net>
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.
prev parent reply other threads:[~2006-11-05 8:27 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
2006-11-05 0:10 ` don
2006-11-05 8:27 ` Thomas Lundquist [this message]
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=20061105082726.GA1158@zelow.no \
--to=lists@zelow.no \
--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