From: Will Newton <will.newton@gmail.com>
To: Bill Cunningham <billcun@suddenlink.net>
Cc: binutils@sourceware.org
Subject: Re: simple program
Date: Thu, 14 Jul 2011 11:18:00 -0000 [thread overview]
Message-ID: <CAFbHwiSbHtC1-ydJL-BZq9n5tMcHQ2AQx1Rn6XzUS5SABr-9=Q@mail.gmail.com> (raw)
In-Reply-To: <000301cc41d1$3dbda1f0$a7d8daad@YOUR1F7593437D>
On Thu, Jul 14, 2011 at 3:53 AM, Bill Cunningham <billcun@suddenlink.net> wrote:
> I am just looking at the library and since everyone seems to start out
> with their first progam being "hello world" is there a way to do that with
> BFD? Maybe calling bfd_init(void) and then simply using bfd_perror to print
> a string? Or would there be a better way?
It depends what you want to do - bfd_perror isn't necessarily that
representative of the BFD API as a whole. It might be useful to start
with one of the smaller binutils programs and learn from that. size.c
seems like it might be a good candidate.
next prev parent reply other threads:[~2011-07-14 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 3:57 Bill Cunningham
2011-07-14 11:18 ` Will Newton [this message]
2011-07-15 10:55 ` Nick Clifton
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='CAFbHwiSbHtC1-ydJL-BZq9n5tMcHQ2AQx1Rn6XzUS5SABr-9=Q@mail.gmail.com' \
--to=will.newton@gmail.com \
--cc=billcun@suddenlink.net \
--cc=binutils@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).