<div dir="auto">Patrick,<div dir="auto"><br></div><div dir="auto">It has been a long time since I touched the PHP bonding build process. But the basic shortcoming you are encouraging is that Swig lacks support for converting a list from C++ into PHP.</div><div dir="auto"><br></div><div dir="auto">This isn't because PHP has no list, but because Swig bindings for PHP never got it added, at least not with the filename the other languages have.</div><div dir="auto"><br></div><div dir="auto">You will need to either go to the upstream Swig project and submit that feature, or write one and bundle it just for the PHP bindings directly in Sword. It's also possible the feature or include file is just different in PHP from Python and Perl, so if you discover that, then you could update our bindings to include the proper file. Obviously, in the spirit of FOSS collaboration, doing engagements directly in Swig would be preferred. Until then, PHP bindings will be unavailable unless you develop some other workaround to missing lists.</div><div dir="auto"><br></div><div dir="auto">--Greg</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 12, 2023, 23:06 Patrick Stephan <<a href="mailto:pstephan1187@gmail.com">pstephan1187@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div name="messageBodySection">
<div dir="auto">Alright... So I've gotten a little bit farther...<br>
<br>
I was missing the `libtoolize --force` command before autogen. After including that command and replacing the php4 references with php8 in the php.m4, Makefile.am, and Makefile.in, I no longer get the "No rule to make target 'phpswig'. Stop." error.<br>
<br>
When I run the `make phpswig` command, this is what I get:<br>
```<br>
mkdir -p php<br>
/usr/bin/swig -php -c++ -o php/Sword.cxx -I. -I/usr/include/sword ./sword.i<br>
templates.i:3: Error: Unable to find 'std_list.i'<br>
make: *** [Makefile:972: phpswig] Error 1<br>
```<br>
<br>
That `std_list.i` file appears to be a swig file that is in its python and perl files, but not in its php files. I imagine that is what is causing this error. Does anyone know how to overcome this?<br></div>
</div>
<div name="messageSignatureSection"><br>
- Patrick</div>
<div name="messageReplySection">On Apr 12, 2023 at 1:50 AM -0500, Peter von Kaehne <<a href="mailto:refdoc@gmx.net" target="_blank" rel="noreferrer">refdoc@gmx.net</a>>, wrote:<br>
<blockquote type="cite">I am not on my computer and speak from old memory but there is a two-step for Perl so I guess that may be for php too .<br>
<br>
<br>
<br>
Sent from my phone. Please forgive misspellings and weird “corrections”<br>
<br>
<blockquote type="cite" style="border-left-color:grey;border-left-width:thin;border-left-style:solid;margin:5px 5px;padding-left:10px">On 12 Apr 2023, at 06:46, Patrick Stephan <<a href="mailto:pstephan1187@gmail.com" target="_blank" rel="noreferrer">pstephan1187@gmail.com</a>> wrote:<br>
<br>
<br>
Hello!<br>
<br>
First off, I want to thank everyone for their work in this project. It's an incredible work to make God's word more readily available.<br>
<br>
As the subject of the email suggests, I am trying to interface with the sword library with PHP. I am attempting to use the SWIG bindings provided, but there are no current PHP bindings provided. There does appear to be some older PHP 4 (PHP 8 is the current major version available) references in the Makefiles and configure file in `bindings/swig/package/` and a php4.m4 file. Attempting to run `make phpswig` (when you might run `make perlswig` according to the readme file in the swig directory) returns a "No rule to make target 'phpswig'. Stop." error. I have made some attempts to replace `php4` with `php8`, but that changes nothing. Anyway, I am attempting to create (or revive) PHP bindings for the sword library and would love some direction on where/how to get started. I have practically no experience with c/c++ or make files or swig, but if someone could give me a shove in the right direction, I think I can figure it out.<br>
<br>
Thank you everyone!<br>
<br>
- Patrick<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" target="_blank" rel="noreferrer">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" target="_blank" rel="noreferrer">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br></blockquote>
</div>
</div>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org" target="_blank" rel="noreferrer">sword-devel@crosswire.org</a><br>
<a href="http://crosswire.org/mailman/listinfo/sword-devel" rel="noreferrer noreferrer" target="_blank">http://crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</blockquote></div>