I'm able to create xls files with poi4r just fine but for some reason
any ruby script that requires poi4r hangs at the end. Has anyone ever
experienced this? Or possibly have some ideas as to what causes it.
b.rb:
require 'release/poi4r'
puts 'test'
strace ruby b.rb:
...
write(1, "test\n", 5te
poi4r.so? or put libgcj in LD_LIBRARY_PATH?
>
> Also, the version of Swig i used was, i believe, 1.3.27. Which is not to say
> other versions wont work... we need to do some more experimentation...
>
>
> On Thursday 22 Mar 2007 10:08:25 pm Jeff Swensen wrote:
>
>>
s for what the issue is. Any ideas?
Jeff Swensen wrote:
> I am attempting to write my own C wrapper for the POI Ruby bindings and
> am looking for some guidance. I compiled poi4r using the swig wrapper
> only to result in a segfault which I'm unable to track down. It also
My mistake, I'm using 1.3.31.
Jeff Swensen wrote:
> Thanks for the responses.
>
> Avik,
>
> What version of SWIG has worked the best for you? The version installed
> here is 1.1 (patch 5). I see that is the most recent stable release.
>
> Thanks,
> Jeff
>
rew C. Oliver wrote:
>
>> Okay from Ruby on Linux...yes POI-ruby is probably your best option
>>
>> I thought you were doing from C on Linux Hopefully Avik is around
>> and he can help... I'll ping him if he doesn't answer.
>>
>> Jeff Swensen
those...doesn't make sense to use C->Ruby->POI
>
> Jeff Swensen wrote:
>> I am attempting to write my own C wrapper for the POI Ruby bindings and
>> am looking for some guidance. I compiled poi4r using the swig wrapper
>> only to result in a segfault which I'm
I am attempting to write my own C wrapper for the POI Ruby bindings and
am looking for some guidance. I compiled poi4r using the swig wrapper
only to result in a segfault which I'm unable to track down. It also
seems that swig generates a lot of unnecessary bloat while creating the
wrapper, which
