These are chat archives for symengine/symengine

14th
Oct 2015
Isuru Fernando
@isuruf
Oct 14 2015 14:05
@abinashmeher999, have you used DevKit with ruby to build ruby extensions in Windows?
Ondřej Čertík
@certik
Oct 14 2015 16:50
@isuruf just googling around brings e.g.: http://stackoverflow.com/questions/185326/whats-a-dll-a-file
Isuru Fernando
@isuruf
Oct 14 2015 16:51
@certik, there's a symengine.dll and libsymengine.dll.a file when built as a shared library, but mkmf generates generator.so (from json gem)
Ondřej Čertík
@certik
Oct 14 2015 16:53
I don't know these tools. I would google around, many times you can find answers that way. If not then we need to ask some Ruby gurus.
For now I would disable or ignore the Windows builds for Ruby, just use linux.
As far as symengine and symengine.py, does everything work, or is there something still to be done?
Isuru Fernando
@isuruf
Oct 14 2015 16:54
Yeah. Travis PR is here symengine/symengine.rb#3
Ondřej Čertík
@certik
Oct 14 2015 16:55
Both repositories became much cleaner now. So I like it.
Isuru Fernando
@isuruf
Oct 14 2015 16:55
We need to update symengine commit hash in symengine.py to make sage tests pass
Also symengine has some more .py files that need to be removed (setup.py and benchmarks)
Ondřej Čertík
@certik
Oct 14 2015 16:55
Yes, they should all be removed.
Excellent, things look good.
Isuru Fernando
@isuruf
Oct 14 2015 17:00
Remove .py files symengine/symengine#618
Ondřej Čertík
@certik
Oct 14 2015 17:11
Travis didn't pick up the PR?
Isuru Fernando
@isuruf
Oct 14 2015 17:12
That's strange
It picked up the build in my fork, but not in the PR
Ondřej Čertík
@certik
Oct 14 2015 17:14
I don't know, the hook is still there.
I removed Travis from the hooks and I am adding it again
Ondřej Čertík
@certik
Oct 14 2015 17:20
It doesn't work. It's probably a Travis bug...
Isuru Fernando
@isuruf
Oct 14 2015 17:20
Shall I send a new PR?
Ondřej Čertík
@certik
Oct 14 2015 17:20
try to send a test PR
Isuru Fernando
@isuruf
Oct 14 2015 17:22
I sent another one. It's not working
Abinash Meher
@abinashmeher999
Oct 14 2015 17:25
@isuruf No I haven't. I heard it from you. Does this use a different API? I will see how this works and see If I can find out what is wrong with the PR.
Ondřej Čertík
@certik
Oct 14 2015 17:50
@isuruf the way Travis is setup seems hard to debug, but if we set it up using the manual webhook, then github shows all communication, so we can see if github sent Travis a message and what response Travis did. So we can either wait if it fixes by itself, or we can debug it by switching to manual webhook and make sure it's not github's fault, and what exactly the Travis response is to each webhook. Then we'll go from there --- probably reporting the problem to Travis if we can't figure out how to fix it ourselves.
Isuru Fernando
@isuruf
Oct 14 2015 17:53
Manual webhook sounds okay to me
Ondřej Čertík
@certik
Oct 14 2015 18:08
I don't have time right now to debug it --- do you want to go ahead? Do you have the necessary permissions?