good point. i was especially looking at this code as something to use going forward, so I wasn't specifically going to support pre-7.4 pikes, unless someone wanted to do it for me :)
bill
On Fri, 24 Oct 2003, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
Afaics it doesn't use the -x module system. It definitely should for 7.4 and later. Some examples:
> /usr/local/bin/pike -x module --query include_path /usr/local/pike/7.4.25/include/pike > /usr/local/bin/pike -x module --query src_path /usr/local/pike/7.4.25/include/pike > /usr/local/bin/pike -x module --query bin_path /usr/local/pike/7.4.25/include/pike(src_path and bin_path might be different when running directly from the build tree.)
/ Martin Stjernholm, Roxen IS
Previous text:
2003-10-23 22:53: Subject: autoconf macros for pike
I made some changes to the autoconf macro that is used to find a pike. It seems to work a little bit better, though it has one shortcoming I'd like to fix: if you specify a pike that's actually a symlink to another, it won't follow the symlink to determine what the actual filename is. This creates a problem when you install a new version of pike (which is a relatively common occurrence), and things stop working because the version has changed:
/usr/local/bin/pike is actually /usr/local/pike/ver/bin/pike.
Any thoughts about this?
-- Specifically, I made some portability changes and added the ability to check for minimum and maximum pike versions. This macro makes it easier to get pike modules set up, as it sets a number of autoconf substitutions.
Example in a configure.in/ac when this file is stored as aclocal.m4 in your project directory:
AP_CHECK_PIKE(7.4.1, 7.4.999)
to check for a version of pike that's between 7.4.1 and 7.4.999, and make sure it has a C include directory (where the headers and compile tools live).
It sets the following variables/substitutions:
PIKE - path to pike PIKE_VERSION - version of pike found (ie 7.4.10) PIKE_INCLUDE_DIRS - string to includes (ie -I /usr/local/pike/7.4.10/include/pike) PIKE_MODULE_DIR - path to pike modules directory (ie /usr/local/pike/7.4.10/lib/modules)0
I'd like to get some feedback on this, along with other suggestions for easing the creation of pike modules and applications. Thanks again!
Bill
H. William Welliver / Fairchild Semiconductor Mountain Top Systems email: bill.welliver@fairchildsemi.com / phone: 570.474.6761 x4445 cell: 570.262.7151
/ Brevb�raren