public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@ecoscentric.com>
To: ecos-patches@sourceware.org
Subject: add global warnings flag to hal/common
Date: Mon, 02 Feb 2009 13:46:00 -0000	[thread overview]
Message-ID: <pn63jtgdf5.fsf@delenn.bartv.net> (raw)

This is part of the compiler flags update. It adds a new option
CYGBLD_GLOBAL_WARNFLAGS holding all the standard warning-related flags
which then gets incorporated into all the CYGBLD_GLOBAL_CFLAGS default
settings. Note that -Winline has been removed and -Wno-write-strings
has been added.

Doing things this way is only a small step towards sorting out the
compiler flags properly. That involves a great many complications,
probably best left to a future release.

Bart

2009-01-31  Bart Veer  <bartv@ecoscentric.com>

	* cdl/hal.cdl: add CYGBLD_GLOBAL_WARNFLAGS, as part of global
	compiler flags update.

Index: cdl/hal.cdl
===================================================================
RCS file: /cvs/ecos/ecos/packages/hal/common/current/cdl/hal.cdl,v
retrieving revision 1.24
diff -u -p -r1.24 hal.cdl
--- cdl/hal.cdl	29 Jan 2009 17:49:13 -0000	1.24
+++ cdl/hal.cdl	2 Feb 2009 13:31:59 -0000
@@ -72,6 +72,16 @@ cdl_package CYGPKG_HAL {
         $(CC) $(CFLAGS) -nostdlib -Wl,-r -T /dev/null -Wl,--whole-archive -o $@ $<
     }   
 
+    cdl_option CYGBLD_GLOBAL_WARNFLAGS {
+        display     "Standard compiler warning flags"
+        parent      CYGBLD_GLOBAL_OPTIONS
+        flavor      data
+        no_define
+        calculated { "-Wall -Wpointer-arith -Wstrict-prototypes -Wundef -Woverloaded-virtual -Wno-write-strings " }
+        description "
+            This option specifies the default warning-related compiler flags used
+          on all eCos platforms."
+    }
 
     cdl_component CYGPKG_HAL_COMMON {
         display       "Platform-independent HAL options"

                 reply	other threads:[~2009-02-02 13:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pn63jtgdf5.fsf@delenn.bartv.net \
    --to=bartv@ecoscentric.com \
    --cc=ecos-patches@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).