Hi all,
I created a C1.hpp and C1.cpp, compiled and linked into a C1.a
file. I did copy the C1.a file into /usr/local/apache2/lib and
C1.hpp into /usr/local/apache2/include. This class provides
some usefull methods to process a request.
OK. Now I would like to use it in my module mod_xyz.
Entering
Hi,
You're using C++ classes in C code. That's not possible and you can fix this
either by rewriting your C++ code in C, or either by doing C wrappers (look
for usage of extern C).
Good luck.
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Laszlo
Envoyé : vendredi
Could you give me an example of a wrapper?
Thank you.
--
László Graf
Frédéric Bor wrote:
Hi,
You're using C++ classes in C code. That's not possible and you can fix this
either by rewriting your C++ code in C, or either by doing C wrappers (look
for usage of extern C).
Good luck.
-Message
In the idea, you have to do something like this:
C1_wrappers.h:
#ifdef __cplusplus
extern C {
#endif
typedef void * C1_OBJECT;
C1_OBJECT C1_create();
void C1_destroy(C1_OBJECT p);
int C1_func_call(C1_OBJECT p, int param1, const char * param2);
#ifdef __cplusplus
}
#endif
C1_wrappers.cpp:
On Wed, Feb 23, 2005 at 10:22:12PM +, Nick Kew wrote:
William A. Rowe, Jr. wrote:
As to Nick's comment, I certainly agree with your position, there
is not enough adoption of APR to -not- roll in the apr/apr-util
Isn't that chicken-and-egg? APR is seen as part of Apache(httpd)
by
Joe Orton said:
Hey! All you folks out there who were having build issues - don't worry,
help is at hand. With *this* release you just have to get *three*
tarballs configured and built correctly together instead of one! It's
*so* much better for you, can't you tell? /sarcasm
Three? You
And I suppose that I have to include the C1_wrappers.h
in C1_wrappers.cpp. OK.
After that I also have to compile and link the C1_wrapper.cpp
into a lib file and copy it into /usr/local/apache2/lib.
Right ?
--
László Graf
Frédéric Bor wrote:
In the idea, you have to do something
On Feb 24, 2005, at 1:52 AM, Justin Erenkrantz wrote:
--On Wednesday, February 23, 2005 10:37 PM -0600 William A. Rowe,
Jr. [EMAIL PROTECTED] wrote:
Uhm, no. By that definition, all the pollution spewed from typical
Linux libraries would be considered 'public api.' Other platforms
are using
--On Wednesday, February 23, 2005 3:07 AM +0100 Branko ?ibej [EMAIL PROTECTED]
wrote:
A number of public functions in mod_dav.h aren't properly exported with
DAV_DECLARE. This recently became a problem for Subversion, because
mod_dav_svn now supports DAV locking, and mod_dav's locking functions
Justin Erenkrantz wrote:
--On Wednesday, February 23, 2005 3:07 AM +0100 Branko ?ibej
[EMAIL PROTECTED] wrote:
A number of public functions in mod_dav.h aren't properly exported with
DAV_DECLARE. This recently became a problem for Subversion, because
mod_dav_svn now supports DAV locking, and
--On Friday, February 25, 2005 10:35 PM +0100 Branko ?ibej [EMAIL PROTECTED]
wrote:
Ah! I'm afraid you seem to have failed. trying, anyway. This would probably
work:
env LANG=en_US.UTF-8 svn propedit --revprop -r??? svn:log
https://svn.apache.org/repos/asf/httpd/httpd
then paste in the name
Justin Erenkrantz wrote:
--On Friday, February 25, 2005 10:35 PM +0100 Branko ?ibej
[EMAIL PROTECTED] wrote:
Ah! I'm afraid you seem to have failed. trying, anyway. This would
probably
work:
env LANG=en_US.UTF-8 svn propedit --revprop -r??? svn:log
12 matches
Mail list logo
