Re: skeleton module?
| From: | bob at thestuff dot net | Date: | Fri, 09 Jun 2000 12:20:15 +0000 |
| Subject: | Re: skeleton module? | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-20719@lists.php.net to get a copy of this message | ||
libtoolize is not part of php. its part of the autoconf/automake series of
tools. :)
On Thu, 8 Jun 2000, er g wrote:
> Hi Jouni,
>
> Your create_module script is exactly what I'm looking
> for. I'm an experienced C programmer, but I'm new to
> PHP. I've been trying to create my own extension, but
> have had no luck. I tried the ext_skel script and
> followed its instructions, but that didn't work. I
> also tried creating a self contained extension by
> following the instructions in the
> README.SELF-CONTAINED-EXTENSIONS file and that was
> broken too. The phpize script it refers to calls
> "libtoolize" which doesn't exist in the php4.0.0
> distribution.
>
> If you could point me to your "create_module" script,
> I'd love to give it a try. Also, I'm wondering if
> there's any roadmap, guidelines or documentation
> regarding the php build environment.
>
> Thanks,
>
> Eric
> --- Sascha Schumann <sascha@schumann.cx> wrote:
> > On Fri, 9 Jun 2000, Jouni Ahto wrote:
> >
> > > In the beginning, I just thought about rewriting
> > magick (ImageMagick)
> > > module from PHP3. But after starting to write it
> > from scratch, a thought
> > > came... there's a lot of necessary things to write
> > when starting a new
> > > module, the minimal code needed seems to be always
> > the same, so why in the
> > > hell not write a script to do it?
> > >
> > > So, I took ext_skel as a starting point, wrote
> > some skeleton code (not
> > > exactly finished or perfect yet), and now I've got
> > a script called
> > > create_module. When you call it like
> > 'create_module foobar', it creates
> > > directory ext/foobar and files Makefile.in,
> > config.m4, foobar.c,
> > > php_foobar.h and foobar.php in it.
> > >
> > > After just tweaking config.m4 and doing
> > ./buildconf; ./configure
> > > --[with|enable]-foobar, it's ready to be compiled
> > in PHP4 and contains
> > > even one example function, foobar_test() (that's
> > why there's that
> > > foobar.php file, to check that the tests in
> > config.m4 went through and the
> > > module was compiled in).
> > >
> > > Thoughts? To myself, seems a really good idea
> > (wouldn't have bothered
> > > otherwise). Should I just add and commit it, so
> > you can see what I'm
> > > trying to do.
> >
> > Sounds neat. Can you integrate it into ext_skel?
> >
> >
> > - Sascha
> >
> >
> > --
> > PHP Development Mailing List <http://www.php.net/>
> > To unsubscribe, e-mail:
> > php-dev-unsubscribe@lists.php.net
> > For additional commands, e-mail:
> > php-dev-help@lists.php.net
> > To contact the list administrators, e-mail:
> > php-list-admin@lists.php.net
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Photos -- now, 100 FREE prints!
> http://photos.yahoo.com
>
> --
> PHP Development Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: php-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>