Since Peter was the only person with an immediate need for the Perl bindings
and he said he doesn't use bzr, I didn't bother pushing a branch anywhere. I
can do that when I get home in a few minutes if you'd like.

Python is already subversion because it was only cmake changes. Perl
required changes to the binding files themselves, thus the need for someone
to either commit the change for me or the need to get write permissions to
that directory.

And yes, CMake is very efficient in both time and screen usage!

--Greg

On Aug 19, 2010 5:58 PM, "Matthew Talbert" <[email protected]> wrote:
> Looks like I just missed you in #sword. Do you have this published in
> a bzr branch somewhere?
>
> By the way, nice work on cmake. The whole process seems quite a bit
> faster than autotools.
>
> Matthew
>
> On Thu, Aug 19, 2010 at 5:17 PM, Greg Hellings <[email protected]>
wrote:
>>
>> Dear List,
>>
>> I have edited the bindings and the Perl test script, such that the
>> Perl bindings now compile with CMake under SWORD.  I believe that the
>> changes I made will also allow compilation under autotools, but as
>> always, YMMV on that.  I'll get that tested once I have a chance to
>> merge all my changes together.  I can't commit them to SVN since I
>> don't have write permissions into the SWIG bindings directory.  Troy -
>> could you give me permissions in bindings/swig/?
>>
>> --Greg
>>
>> _______________________________________________
>> sword-devel mailing list: [email protected]
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
> _______________________________________________
> sword-devel mailing list: [email protected]
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: [email protected]
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to