-
Notifications
You must be signed in to change notification settings - Fork 96
Streamline mex build and install process #140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hmm. I'm going to turn off these comments from coveralls -- the info is there in the status box with the Travis status. |
import os | ||
import sys | ||
import shutil | ||
import glob | ||
from distutils.core import setup |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment below says distutils
was imported later on purpose. (I'm not really familiar with why though).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see (I guess), I'll move it.
Looks good overall. I built the Octave messenger on my mac and it worked fine. The Windows thing I guess is an upstream problem? I'm OK with merging this after you address the (tiny) comments I made. I just tried it out and the Octave and MATLAB mex files apparently can coexist in the same directory, and each program will pick up the right one. At this point we could start including pre-built binaries for Octave too. |
Wow, what a nightmare on Windows:
3.6.4 Visual Studio:
3.6.4 Mingw:
Cygwin 3.8.2:
I tried installing the |
I was hoping to phase out |
@isbadawi, ready to roll! |
Streamline mex build and install process
As of arokem/python-matlab-bridge#140, a pre-built messenger.mex is included for Octave on Linux.
Nice job. There was one small thing left over from this. See: On Mon, Feb 16, 2015 at 8:37 AM, Ismail Badawi [email protected]
|
Unfortunately, I could not get it working in Windows: http://savannah.gnu.org/bugs/?41833. See my comment below for the gory details.