Hi,
I have added support for static linking of mod_jk (for
Apache-1.3.x). I have
used automake to reach it, it has side effects I would like to comment:
- apxs cannot be used build mod_jk.so.
- It needs autoconf/automake for prepare the *.in file. (Only
for develloppers).
- It needs libtools.
GOMEZ Henri wrote:
Hi,
I have added support for static linking of mod_jk (for
Apache-1.3.x). I have
used automake to reach it, it has side effects I would like to comment:
- apxs cannot be used build mod_jk.so.
- It needs autoconf/automake for prepare the *.in file. (Only
for
Error - it shouldn't be in common...
Are you sure ?
in jk_jni_worker there is a jni_worker_factory() which is
referenced in jk_worker_list.h which is used to determine
workers in jk_worker.c (get_factory_for).
If jk_jni_worker is removed from common, it should be also
removed from the list
[EMAIL PROTECTED] wrote:
On Tue, 15 May 2001, jean-frederic clere wrote:
By the way I have a question: Why jk_jni_worker.c is in common not in jni? What
it is used for? (I have to add JAVA_HOME to the configure for it and I am
curious).
Error - it shouldn't be in common...
But it
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Currently I have just prepared it for Apache2.0 and Apache1.3,
before going on I
have some questions:
I tested the configure/makefile stuff and it works well but
could you also add the java detection for JNI
GOMEZ Henri wrote:
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Currently I have just prepared it for Apache2.0 and Apache1.3,
before going on I
have some questions:
I tested the configure/makefile stuff and it works well but
could you also add
[EMAIL PROTECTED] wrote:
On Mon, 14 May 2001, jean-frederic clere wrote:
Hi,
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Excelent !
Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I
have some questions:
The configure.in assumes that the Apache connectors
sub-directories are
apache-1.3 and apache-2.0. I think that more consistant
with mod_webapp.
done
My idea is to build one connector per call of configure/make,
--with-java should
build the JNI support, correct?
I have noted that common contains jk_jni_worker.c, should not
we move it in jni?
no, jk_jni_worker could also be used into apache 1.3/2.0.
And that's HOW IBM use mod_jk on at least
Wow, it is so good to see development discussion on tomcat-dev, and be
able to participate :-)
I have a big question - what happens if configure/libtool is used and
different options are given for mod_jk and apache ?
I can't give a concrete example, but APXS had the big benefit that it
cached
On Tue, 15 May 2001, jean-frederic clere wrote:
By the way I have a question: Why jk_jni_worker.c is in common not in jni? What
it is used for? (I have to add JAVA_HOME to the configure for it and I am
curious).
Error - it shouldn't be in common...
jk_jni_worker uses JNI to start tomcat in
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Thanks great works :!
Currently I have just prepared it for Apache2.0 and Apache1.3,
before going on I
have some questions:
- The idea is to have one configure.in in
jakarta-tomcat-connectors/jk/src/native and
On Mon, 14 May 2001, jean-frederic clere wrote:
Hi,
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Excelent !
Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I
have some questions:
- The idea is to have one
13 matches
Mail list logo
