Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming > #8589

Re: U-boot Standalone Examples - Hello_world.c

From Wouter Verhelst <w@uter.be>
Newsgroups comp.programming
Subject Re: U-boot Standalone Examples - Hello_world.c
Date 2018-03-29 16:34 +0200
Organization A noiseless patient Spider
Message-ID <h5avoe-ae7.ln1@gangtai.grep.be> (permalink)
References <32138b9e-84f1-46c8-876a-d1884e30b8a0@googlegroups.com>

Show all headers | View raw


On 28-03-18 20:23, Ilias Abrams wrote:
> Hi guys, 
> 
> I was looking into the standalone example (hello_world) 
> that U-boot repository contains and builds when you build and compile U-boot. 
> 
> It has those two libraries at the top, and I was wondering, 
> where the program finds those libraries? Where those headers located? 

For clarity, "header files" and "libraries" are not the same thing. A
header file is meant to contain function declarations, constants, and
macros that a programmer may be able to use in a program. A library is a
body of compiled code that a program may link to.

> There are not into the U-boot directory. 
> A Makefile defines where the compiler will find the header? 

Usually, the build system (which may, but is not required to be, a
Makefile) will indeed have to define where such headers are to be found.

Most compilers accept a "-I" argument to pass extra include paths to the
preprocessor; if you search the Makefile for such options, you should be
able to figure out where the header files in question are to be found.

Regards,

Back to comp.programming | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

U-boot Standalone Examples - Hello_world.c Ilias Abrams <iliasabrams@gmail.com> - 2018-03-28 11:23 -0700
  Re: U-boot Standalone Examples - Hello_world.c Wouter Verhelst <w@uter.be> - 2018-03-29 16:34 +0200

csiph-web