All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luigi 'Comio' Mantellini <luigi.mantellini@idf-hit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Identify an U-boot compilation
Date: Fri, 14 Mar 2008 14:43:39 +0100	[thread overview]
Message-ID: <1205502219.21112.30.camel@localhost> (raw)

Hi All,

Is there a symbol (like __U_BOO_T__) that is defined during U-Boot
compilation and that I can test into my .c/.h source files?

I have a self-made library that is shared between the bootloader and the
linux kernel.
Obviously the source paths and includes are different in the two
environment and I need to choose the correct code on the basis of the
target enviroment.

In the linux kernel I can use symbol like "__LINUX__" to understand that
the actual compilation is referred to the Linux Kernel... but I don't
find an similar symbol define in U-Boot.

I would write code like:
...
#if defined(__U_BOOT__)
/* U-boot specific code */
...
#elsif defined(__LINUX__)
/*Kernel specific code */
#endif
...

Is there a similar mechanism in U-BOOT building infrastructure? (anyway,
can we insert a -D__U_BOOT__ in the compiler invocation?)

Thanks a lot,

luigi

-- 
     ______       Luigi Mantellini
   .'______'.     R&D - Software
  (.'      '.)    Industrie Dial Face S.p.A.
  ( :=----=: )    Via Canzo, 4
  ('.______.')    20068 Peschiera Borromeo (MI), Italy
   '.______.'     Tel.: +39 02 5167 2813
                  Fax:  +39 02 5167 2459
Ind.  Dial Face   Email: luigi.mantellini at idf-hit.com
www.idf-hit.com   GPG fingerprint: 3DD1 7B71 FBDF 6376 1B4A
                                   B003 175F E979 907E 1650

             reply	other threads:[~2008-03-14 13:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-14 13:43 Luigi 'Comio' Mantellini [this message]
2008-03-24 11:38 ` [U-Boot-Users] Identify an U-boot compilation Luigi 'Comio' Mantellini

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=1205502219.21112.30.camel@localhost \
    --to=luigi.mantellini@idf-hit.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.