Re: Per-source CFLAGS

From: Marcel Moolenaar (marcel_at_xcllnt.net)
Date: 06/22/03

  • Next message: David Schultz: "Re: Per-source CFLAGS" 
    Date: Sat, 21 Jun 2003 21:55:29 -0700
To: arch@FreeBSD.ORG

    On Sat, Jun 21, 2003 at 05:51:24PM -0700, David Schultz wrote:
    > The following patch adds support for per-file CFLAGS, which gets
    > appended to the command line after the global CFLAGS.

    Per file compilation options are in direct conflict with make
    invocator control, by way of it being a makefile writer knob.
    Put differently: it's a feature for developers, not builders.
    We already see the problem with that when we define CFLAGS on
    the make command line, rather than in the environment. I'm
    not opposed to per-file options, but it seems to push the
    need to split make invocator knobs from makefile writer knobs.
    Until we have such seperation, I request that per-file options
    be made conditional so that make invocators still have control
    without being powerless. 

    -- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: David Schultz: "Re: Per-source CFLAGS"

    Relevant Pages

    • Re: Per-source CFLAGS
      ... >> I intend to use this feature for gdtoa, ... > Do you need to turn off all warnings or just ones for non-broken ... Per-file CFLAGS can't be used to disable warnings both selectively ...
      (freebsd-arch)
    • Re: make buildworld fails:: cmap.h: No such file or directory
      ... >> When I do a make buildword, I get a bunch of .h files not found: ... The command should have been ... this likely happens because you pass CFLAGS on the make's ...
      (freebsd-stable)
    • Re: HEADS UP: Ports are not ready for CFLAGS=-O2 in 6.0
      ... the goal of PORT_CFLAGS is to bring the possibility to specify ... > needs to be usable even if CFLAGS is specified. ... If nothing regarding CFLAGS is given in the command line, port is ...
      (freebsd-current)
    • Re: using libparanoia
      ... > be protected by libparanoia? ... if you put -lparanoia in CFLAGS it will be too early on the ... command line to have any effect. ... To unsubscribe, ...
      (FreeBSD-Security)