All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Wozniak <awozniak@mc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] -nostdinc
Date: Wed, 09 Mar 2005 09:37:25 -0500	[thread overview]
Message-ID: <422F0A25.3080109@mc.com> (raw)
In-Reply-To: <20050309093922.9DE4DC1510@atlas.denx.de>

Thanks for the kind reply.

Wolfgang Denk wrote:
> In message <422E60FD.50108@mc.com> you wrote:
> 
>>Having lots of fun with U-boot on our custom PPC440GX board. We're also 
>>pretty far along on developing a loadable "u-boot application" for this 
>>board.
> 
> Congrats :-)
> 
>>I've noticed that -nostdinc is used for many of the compiles. When I 
> 
> It should be used for _all_ compiles of files that  get  linked  into
> the U-Boot image. Please point out if we're missing any (of course it
> is  NOT  used  for  any  tools that will run on the host system, like
> mkimage etc.).

I haven't seen any yet.

>>attempted to include stdlib.h and atoi() in our application, the 
>>compiler could not find the file.
> 
> That's a good thing as it prevented you to do a stupind thing ;-)
> 
>>Further examination of the U-Boot code-base shows little or no use of 
>>stdlib.h. Is this to keep the overall binary size to a minimum?
> 
> It is to  make  U-Boot  self-contained,  i.  e.  independent  of  any
> external libraries etc.

That's a good thing.

>>Any other reason for not adding this library to build? One simple 
> 
> Yes. You don;t need it.
> 
>>alternative is to include our own atoi() source code.
> 
> Don't reinvent the wheel. Don't bloat the code by multiple  implemen-
> tations of the same function. Use simple_strtoul() instead.

Ahhh, I was wondering how U-Boot handled this common task. I didn't look 
far enough.

> Best regards,
> 
> Wolfgang Denk
> 

      reply	other threads:[~2005-03-09 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  2:35 [U-Boot-Users] -nostdinc Andrew Wozniak
2005-03-09  9:39 ` Wolfgang Denk
2005-03-09 14:37   ` Andrew Wozniak [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=422F0A25.3080109@mc.com \
    --to=awozniak@mc.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.