On 7/12/07, Dale Worley <[EMAIL PROTECTED]> wrote:
Yes, you should be careful to set preprocessor symbols only through the correct build environment variable, and they should be the same for all components. In this case, something like: export CFLAGS="-DHAVE_SPEEX" export CXXFLAGS="-DHAVE_SPEEX" ./configure ... (The values of the env. vars. are sampled and saved when ./configure is run.)
I assign these precompiler macros by throwing all of them in a shell script that sets the vars and does the configure all for you, so you're guaranteed to have the same vars every time..: #!/bin/sh export CFLAGS="$CFLAGS -DHAVE_SPEEX" export CXXFLAGS="$CXXFLAGS -DHAVE_SPEEX" autoreconf --force --install ./configure --disable-sipviewer $@ Doing it this way makes vars consistent across all projects, allows you to specify custom options to configure, and provide more flexibility setting CFLAGS and CXXFLAGS..., as you can also set it on the command line to add a define you only want for a particular project - say, sipXtackLib.. you can do: CFLAGS="-DSOME_ENABLE_FEATURE" CXXFLAGS="-DSOME_ENABLE_FEATURE" ~/bin/myconfigurescript Also, "make clean" if you are going to change an env. var., as the
makefiles do not know to recompile .o files that are affected.
Just to clarify: makefiles do not know to recompile when there is an *environment variable change* such as this :) -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
