zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Peter Stephenson <pws@csr.com>,
	zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: How to cache $CFLAGS, $LIBS etc.
Date: Fri, 11 Aug 2000 16:37:34 +0000	[thread overview]
Message-ID: <1000811163734.ZM9663@candle.brasslantern.com> (raw)
In-Reply-To: <1000811161610.ZM9646@candle.brasslantern.com>

On Aug 11,  4:16pm, Bart Schaefer wrote:
} Subject: Re: How to cache $CFLAGS, $LIBS etc.
}
} This is lifted (and edited to change the name) from another acinclude.m4
} that I wrote:
}  
} AC_DEFUN([zsh_compile_flags],
}     [AC_ARG_ENABLE(cflags,
} 	[  --enable-cflags=...     specify C compiler flags],
} 	if test "$enableval" = "yes"
} 	then CFLAGS="$1"
} 	else CFLAGS="$enable_cflags"
} 	fi)
}     [AC_ARG_ENABLE(ldflags,
} 	[  --enable-ldflags=...    specify linker flags],
} 	if test "$enableval" = "yes"
} 	then LDFLAGS="$1"
                      ^^
		      That should be "$2".  Sorry about that.
} 	else LDFLAGS="$enable_ldflags"
} 	fi)])

The references to "$1" and "$2" are of course the argument of the m4 macro
when called from configure, not shell positional parameters.  E.g. you can
put in configure.in

zsh_compile_flags(-g3 -O0, -ltermcap)

to cause those to be the defaults for --enable-cflags and --enable-ldflags.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2000-08-12  0:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-11 11:28 Peter Stephenson
2000-08-11 11:32 ` Ollivier Robert
2000-08-11 13:48   ` Trond Eivind Glomsrød
2000-08-11 16:16 ` Bart Schaefer
2000-08-11 16:37   ` Bart Schaefer [this message]
2000-08-11 18:08   ` Peter Stephenson
2000-08-16  7:25 ` Andrej Borsenkow
2000-08-16 12:56   ` Bart Schaefer

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=1000811163734.ZM9663@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=pws@csr.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).