A attempt to explain...
Source-Struktur:
--
PHP-Tree INDI-CVS
ext ...
@indi -->php
*buildconf (php) include
*configure (php)
Hi Markus,
>
> You don't need to include your sources but a static library
> of your extension needs to be created which exports the
> symbols as needed and which gets statically linked into
> libphp4.so .
How you build and link static libs automatically by modifying
config.m4?
On Tue, Jul 02, 2002 at 12:42:08AM +0200, Ron Lange wrote :
> my last question for this week (I hope):
> How can I include the sources of my lib in the php build??? Although it's
> compiling fine, the apache build fails about undefined references to my
> functions. I am really tired now, since
Hello again,
my last question for this week (I hope):
How can I include the sources of my lib in the php build??? Although it's
compiling fine, the apache build fails about undefined references to my
functions. I am really tired now, since four hours I am trying to solve
this problem. May I am
Hi Fab,
I have left out some informations, sorry. I had a problem with including
our lib headers, but now I managed it. Man pages are fine
things...especially these of autoconf ;-). Another mistake I've done was to
ignore the output of the ext-skel script, which is telling the further
steps (.
Not sure why you say that including a header should throw make errors.. if
you didn't change the Makefile, it should have no effect.
What are the errors you're getting?
Fab
>From: Ron Lange <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
>
Hi all,
now I have only one really sucking problem: how I can compile extensions? I
know that I am appearing a little bit stupid, just because of the hints of
Derick an the others in a former thread...
But I can't get it work...
The core code of my extension (without any php-related stuff yet)
