These are chat archives for symengine/symengine
.argsto arrive at a solution in python for now. (It'll obviously be slow than implementing in C++)
When we are packaging using
gem build symengine.gemspec, all the files needed for the gem are put into an archive. When
gem install symengine-0.0.1.gem is given, the archive is extracted to the gems install directory and then if there is a extconf.rb, it is executed to build the package.
To mirror what we do with
setup.py, we have to move
symengine.gemspec to root and add a
extconf.rb to the root as well. Also, ruby wrappers need to be copied to the root via CMake as well. This method is quite hackish, but can be done, although for people who are familiar with ruby may find it hard to understand.
Is this okay? or should we separate the ruby wrappers?
gem build symengine/ruby/symengine.gemspecwill package the files.
gem install symengine-0.1.0.gem --verbosewill install libsymengine and the wrapper
extconf.rb. Are you calling
extconf.rb? If yes, would there be a problem if the user doesn't have cmake installed(is it possible)?