How about the following solution? You save the configuration string in a header file at the configuration time, this way you can use the #include in C/C++ and then hardcode the string.
On Thursday, June 4, 2015, Massimo Manghi <[email protected]> wrote: > good idea, but how did the PHP guys get the configuration string in the > code? Did they have some file holding this sort of things? THere must be a > shell variable in the configure script that holds the exact form used to > run configure itself and it could be stored somewhere along with other > info. Perhaps a bash shell built-in variable? > > -- Massimo > > On 03-06-2015 17:33, Rani Ahmed wrote: > >> Hi. >> >> I noticed that phpinfo() also mentions the compiling options of php. >> What I mean by here is this : >> >> ./configure >> --with-tcl=/usr/lib/tcl8.5/ >> >> --with-apache=/usr/local/apache2 >> --with-apxs=/usr/local/apache2/bin/apxs >> >> >> --with-tclsh=/usr/bin/tclsh8.5 >> --with-rivet-target-dir=/usr/lib/rivet2.2 >> --enable-version-display >> >> So how can I get it from Rivet? >> >> And I know its different from PHP in the sense that Rivet depends on >> the installed Tcl packages, and you guys remember that I printed out >> _[package names] _ >> >> An idea : How about printing also the _./configure _of Tcl >> interpreter?! This would be nice too. I am trying to make it look as >> near as possible to PHP. >> > >
