You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rivet-dev@tcl.apache.org by Rani Ahmed <ra...@gmail.com> on 2015/06/03 18:33:23 UTC
With respect to rivet_info{}
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 it's 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.
Re: With respect to rivet_info{}
Posted by Massimo Manghi <mx...@apache.org>.
configure scripts in branches/2.2 and trunk/ now define
RIVET_CONFIGURE_CMD in rivet_config.h with the whole configure command line.
This definition is copied in the array 'server' in a variable with the
same name.
The code in branches/2.2 is now labeled as 2.2.4 and changes also
feature some rationalization of the code in Rivet_ChildHandlers
-- Massimo
On 06/10/2015 09:42 AM, Rani Ahmed wrote:
> Thank you Massimo.
>
> On Wednesday, June 10, 2015, Massimo Manghi <mx...@apache.org> wrote:
>
>> Dear Rani
>>
>> yes, this looks to be feasible. I will add it to the rivet_config.h file,
>> it should be straightforward, provided there is a shell variable holding
>> the full configure command
>>
>> -- Massimo
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: With respect to rivet_info{}
Posted by Rani Ahmed <ra...@gmail.com>.
Thank you Massimo.
On Wednesday, June 10, 2015, Massimo Manghi <mx...@apache.org> wrote:
> Dear Rani
>
> yes, this looks to be feasible. I will add it to the rivet_config.h file,
> it should be straightforward, provided there is a shell variable holding
> the full configure command
>
> -- Massimo
>
> On 06/04/2015 05:55 PM, Rani Ahmed wrote:
>
>> 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 <ma...@unipr.it>
>> 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.
>>>>
>>>>
>>>
>>>
>>
Re: With respect to rivet_info{}
Posted by Massimo Manghi <mx...@apache.org>.
Dear Rani
yes, this looks to be feasible. I will add it to the rivet_config.h
file, it should be straightforward, provided there is a shell variable
holding the full configure command
-- Massimo
On 06/04/2015 05:55 PM, Rani Ahmed wrote:
> 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 <ma...@unipr.it> 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.
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org
Re: With respect to rivet_info{}
Posted by Rani Ahmed <ra...@gmail.com>.
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 <ma...@unipr.it> 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.
>>
>
>
Re: With respect to rivet_info{}
Posted by Jeff Lawson <je...@bovine.net>.
If I had to guess, their autoconf script is probably just writing the
command-line arguments as a quoted string constant into a .h file that gets
included into the binary during compilation. The "config.status" file will
also have the configure command-line written to the top of it in the
comments, so you probably could use the same variable in the substitution
of the .h file.
On Thu, Jun 4, 2015 at 1:17 AM, Massimo Manghi <ma...@unipr.it>
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.
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
> For additional commands, e-mail: rivet-dev-help@tcl.apache.org
>
>
Re: With respect to rivet_info{}
Posted by Massimo Manghi <ma...@unipr.it>.
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org