Re: How to set CFLAGS for the build step?

[dirk_(_dot_)_meyer_(_at_)_dinoex_(_dot_)_sub_(_dot_)_org (Dirk Meyer)]

Max Laier schrieb:,

> > The makefile of the distribution don't have to include make.conf.
> > To honor CC/CFLAGS/LDFLAGS ...., they have to be passed in the
> > enviroment.
> 
> Okay ... so the attached should fix my problem, right?  But it seems that 
> I'd have to anticipate what kind of settings a user wants in their 
> make.conf, wouldn't I?  While CFLAGS seems to be passed magically, CC or 
> LDFLAGS are not.  I don't care all that much as long as it works for me, 
> but it seems broken.

The flags passed to gmake/configure are limited also.

$ configure --help
[...]
Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  LIBS        libraries to pass to the linker, e.g. -l<library>
  CPPFLAGS    C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags
  CPP         C preprocessor
[...]

And if the bsd makefile don't use some marcos,
you can safly ignore them.

The only problem I see if a ports makefile
uses "bsd.prog.mk" or "bsd.lib.mk".

Linke some tools that had been part of FreeBSD or other BSD's.

kind regards Dirk

- Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
http://people.freebsd.org/~dinoex/errorlogs/
_______________________________________________
freebsd-ports_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe_(_at_)_freebsd_(_dot_)_org"