You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, python setup.py build just runs make under the hood but ignores command-line arguments. For instance, if the compiler is set in the command-line argument, then that compiler should be used. Should be straightforward as calling make argv, once argv has been parsed
The text was updated successfully, but these errors were encountered:
Looks like this is much more difficult! Essentially, people have to do export CC = gcc before calling python setup.py install. In any case, all of the compilation is handled in the Makefile, and users should first make and then make install anyway.
Will make some simple attempts to test before closing this issue.
Currently,
python setup.py build
just runsmake
under the hood but ignores command-line arguments. For instance, if the compiler is set in the command-line argument, then that compiler should be used. Should be straightforward as callingmake argv
, once argv has been parsedThe text was updated successfully, but these errors were encountered: