schrieb Albert Cahalan on 2013-01-27 02:42:
> I've already tried changing AM_CFLAGS in Makefile.am but it seems this
> variable isn't even getting used. 

I'm no expert, but my understanding is that Makefile.am is converted to
Makefile.in with automake by the maintainer. This generates all the
targets and has already all the files, but still some placeholders for
variable. When configure is run by the user/"builder", these variables
are replaced and a proper Makefile (and possibly config.h from
config.h.in) is generated out of Makefile.in.

See
http://www.gnu.org/software/autoconf/manual/autoconf.html#Making-configure-Scripts

> There don't seem to be per-object ones
> either. Running ./configure again doesn't help.

./configure has --help, which gives a hint at the end - ok, it's not
very verbose, but maybe just the right for you:

http://wwSystem types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]

Optional Features:
[...]
  --enable-shared[=PKGS]  build shared libraries [default=yes]
  --enable-static[=PKGS]  build static libraries [default=yes]
[...]

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    (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
              you have headers in a nonstandard directory <include dir>
  CPP         C preprocessor

> I'd like to add flags for:
> 
> a. Compiling the library
> b. Compiling unit tests
> c. Compiling anything else (target only, not build host)
> d. Linking the library

May one of the following works for you:

1) running automake or
2) use --host= or --enable-static etc. or
3) or run CFLAGS="<value>" ./configure ; this should work too:
./configure CFLAGS="<value>" ; CFLAGS will propagate to CPPFLAGS AFAIK.

./configure is a big fat shell script, so you may have a look at it
(grep and friends...) and see what happens to the flags or the
--enable-/--disable-options.

Just of curiosity, what flags do you want to pass, what do you need it for?

Regards

Patrick
-- 
Engineers motto: cheap, good, fast: choose any two
Patrick Strasser <patrick at wirklich priv at>

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to