public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: David Fernandez <david.fernandez.work@googlemail.com>
To: ecos-discuss@ecos.sourceware.org
Cc: Sergei Gavrikov <sergei.gavrikov@gmail.com>,
	Simon Kallweit <simon.kallweit@intefo.ch>
Subject: Re: [ECOS]How to run testprograms for lwip
Date: Thu, 30 Jul 2009 09:11:00 -0000	[thread overview]
Message-ID: <ea104e1b0907300210of7ab77at6ac11777000dd8da@mail.gmail.com> (raw)

> #if defined(CYGFUN_LWIP_IP_FORWARD)
> # define IP_FORWARD 1
> #else
> # define IP_FORWARD 0
> #endif
>
> FYI: There are a few defines like this
>
> #define FOO defined(CYG_FOO)
>
> in lwipopts.h. Small testcase:
>
> #define CYG_FOO 1
> #define FOO defined(CYG_FOO)
>
> main ()
> {
> int foo = FOO;
> }
>
> It cannot be linked. FOO is not boolean ;-) I can check the same
> "rvalues" then and send a patch if you want.
>

May be I'm wrong, but I think that the macro CYG_FUN_LWIP_IP_FORWARD
is not only defined, but defined as 1 if the option is enabled. May be
that what you want is to use the macro directly instead of the
preprocessor operator applied to it.

That is simpler than defining another macro, and if the option is
disabled, the macro would be defined, but its value would be 0.

You might want to check it this way though, in case the lwip is
included, but those CDL options are not active for some reason...
which may be impossible, but here you are.

#ifndef CYG_FUN_LWIP_IP_FORWARD
#define IP_FORWARD 0
#else
#define IP_FORWARD CYG_FUN_LWIP_IP_FORWARD
#endif

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2009-07-30  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30  9:11 David Fernandez [this message]
2009-07-30 11:02 ` Sergei Gavrikov
2009-07-30 11:11   ` Simon Kallweit
  -- strict thread matches above, loose matches on Subject: below --
2009-07-23  9:50 Robert Brusa
2009-07-23 10:02 ` Simon Kallweit
2009-07-23 12:19   ` Robert Brusa
2009-07-23 12:25     ` Simon Kallweit
2009-07-24 15:51       ` Robert Brusa
2009-07-29 12:25       ` Sergei Gavrikov
2009-07-29 12:32         ` Simon Kallweit

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=ea104e1b0907300210of7ab77at6ac11777000dd8da@mail.gmail.com \
    --to=david.fernandez.work@googlemail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=sergei.gavrikov@gmail.com \
    --cc=simon.kallweit@intefo.ch \
    /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).