[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GLPK API change
From: |
Michael Goffioul |
Subject: |
Re: GLPK API change |
Date: |
Thu, 08 Feb 2007 21:27:49 +0100 |
User-agent: |
Thunderbird 1.5.0.9 (Windows/20061207) |
John W. Eaton a écrit :
OK, but what is the right feature test for autoconf in this case? We
should not be encoding version numbers there if at all possible.
The test should check for _glp_lpx_simplex symbol (note the leading
underscore).
But maybe the safest solution is to write a custom test that uses
lpx_simplex instead.
Indeed, the user API hasn't changed, but this API is #define'd in GLPK
headers, and
the symbol to which it's #define'd has changed. For instance:
#define lpx_simplex glp_lpx_simplex
became
#define lpx_simplex _glp_lpx_simplex
So, if you write a custom test that tries to link a piece of code using
lpx_simplex,
this should be portable. OTOH, you must check for the header first, because
you'll need to include it in your custom test.
Michael.