Setup.py For Mac
Windows Good solutions for Windows are, (which both provide binary installers for Windows, OS X and Linux). Both of these packages include Python, NumPy and many additional packages. A lightweight alternative is to download the Python installer from and the NumPy installer for your Python version from the Sourceforge. The NumPy installer includes binaries for different CPU’s (without SSE instructions, with SSE2 or with SSE3) and installs the correct one automatically. If needed, this can be bypassed from the command line with. Prerequisites Building NumPy requires the following software installed:. Python 2.6.x, 2.7.x, 3.2.x or newer On Debian and derivatives (Ubuntu): python, python-dev (or python3-dev) On Windows: the official python installer at is enough Make sure that the Python package distutils is installed before continuing.
For example, in Debian GNU/Linux, installing python-dev also installs distutils. Python must also be compiled with the zlib module enabled. This is practically always the case with pre-packaged Pythons. Compilers To build any extension modules for Python, you’ll need a C compiler. Various NumPy modules use FORTRAN 77 libraries, so you’ll also need a FORTRAN 77 compiler installed. Note that NumPy is developed mainly using GNU compilers.
Compilers from other vendors such as Intel, Absoft, Sun, NAG, Compaq, Vast, Porland, Lahey, HP, IBM, Microsoft are only supported in the form of community feedback, and may not work out of the box. GCC 4.x (and later) compilers are recommended. Linear Algebra libraries NumPy does not require any external linear algebra libraries to be installed. However, if these are available, NumPy’s setup script can detect them and use them for building. A number of different LAPACK library setups can be used, including optimized LAPACK libraries such as ATLAS, MKL or the Accelerate/vecLib framework on OS X.
Command Python Setup.py Egg_info Failed With Error Code 1 Psycopg2 Mac I have been trying to setup a project in Pycharm with psycopg2. If I install it Cleaning. Setup postgresql. To create a postgre user and group, we are going to use netinfo. According to reports, Mas OS X 10.5 Leopard will be stripped of netinfo. These commands are likely to be Tiger only. First, find an unused userID and groupID. Typically anything in the 200s or 300s will be unused on most Mac OS X non-server systems.
FORTRAN ABI mismatch The two most popular open source fortran compilers are g77 and gfortran. Unfortunately, they are not ABI compatible, which means that concretely you should avoid mixing libraries built with one with another.
In particular, if your blas/lapack/atlas is built with g77, you must use g77 when building numpy and scipy; on the contrary, if your atlas is built with gfortran, you must build numpy/scipy with gfortran. This applies for most other cases where different FORTRAN compilers might have been used.
Attachments: so finally I managed to build on mac. The setup.py script was broken (for mac at least), it had wrong -L link paths and it was trying to link to -ltorrent-rasterbar, when what was generated was libtorrent.dylib.1.0.2. The contents of the `linkflags` and `compileflags` files that setup.py uses to build on python were no good for Mac.
A humble question for mac. So I created a series of functions to calculate the proper link and compile flags. Now it builds and links perfectly on MacOSX. I built everything (boost and libtorrent) via the bjam route, and then the last step was invoking the `bindings/python/setup.py` script passing it the `bdist` command. Here's a patch (based on the `setup.py` as it was on 1.0.2) And the `setup.py` file as is on my system. Cheers and thanks On Mon, Nov 17, 2014 at 12:37 AM, arvid wrote: On 2014-11-15 20:13, Angel Leon wrote: ArvidSo I literally spent all day, and documented the whole process into a step by step guide (all compilation output was captured and it is available in the guide) Don't know what else to do to make it work depending a bit on how you want to build libtorrent, I think there are simpler ways.
the two main dimensions of options are: - building with boost-build or with (./autotool.sh)./configure && make - building with boost installed on the system or directly from the source archive This gives you 4 combinations of build options. On linux I would imagine one would typically link against installed boost libraries and on windows one would typically want to build and link against boost from source. the linkflags and compileflags files that live in the bindings/python directory are there to propagate build flags from the configure script to the setup.py script.
This is only necessary when using the autoconf/ makefile build system. When using boost-build, configuration options are automatically propagated. The simplest of the 4 options is probably building using bjam with boost built from source. To do this, you need boost-build installed (which should set the BOOSTBUILDPATH environment variable when installed).
In the bindings/python directory, just run: b2 boost=source -j4 (-j specifies how many parallel builds should be used, just like for make). To build using setup.py for building a python package, run: python setup.py -bjam Building with boost-build against the system boost, just remove the boost=source option: b2 -j4 (the setup.py hard codes using boost=source currently) The makefile, I don't think, supports building against boost from source, but just against the system-installed boost. This is because the main purpose of the autoconf/makefiles is to play nicely with packaging systems. For this, you need to run./configure && make in the root of libtorrent, to build the library and to generate the linkflags and compileflags in the bindings/python directory.
Setup.py Install Mac
Then just run setup.py with appropriate commandline options in the binding/python directory. Still getting this, after rebuilding everything: $./env/bin/python Python 2.7.8 (default, Aug 24 2014, 21:26:19) GCC 4.2.1 Compatible Apple LLVM 5.1 (clang-503.0.40) on darwin Type 'help', 'copyright', 'credits' or 'license' for more information. import libtorrent Traceback (most recent call last): File ', line 1, in TypeError: No topython (by-value) converter found for C type: libtorrent::alert::categoryt If you have a chance to take a look at the guide perhaps you'll quickly see what I'm doing wrong. I just tested head of RC10, to run: b2 boost=source -j4 in the bindings/python directory. This works for me: $ python -c 'import libtorrent as lt' If you want to build against a different version of python (for instance a macports build of python 3.4), you can add this to your user-config.jam file (either in your home directory or in $BOOSTBUILDPATH): using python: 3.4: /opt/local/bin/python34 : /opt/local/Library/Frameworks/Python.framework/Versions/3.4/ include/python3.4m : /opt/local/Library/Frameworks/Python.framework/Versions/3.4/ lib/python3.4/config-3.4m ; The makefile approach requires boost to be installed. To test it I ran (in the root of libtorrent):./autotool.sh./configure make -j4 cd bindings/python python setup.py bdist python -c 'import libtorrent as lt' (which also appears to work). One thing to look out for is if you get an error like this: Traceback (most recent call last): File ', line 1, in ImportError: dynamic module does not define init function (initlibtorrent) The library was built for python 3 but imported into python 2.
Setup.py For Mac Download
If you get an error like this: Traceback (most recent call last): File ', line 1, in ImportError: dynamic module does not define init function (PyInitlibtorrent) You built the library for python 2 and are importing it into python 3. The version the module is built for is determined by PYVERSIONHEXwhich presumably is set by some python header file. - Anyway, looking at the error message you get, it suggests that somehow, the alert::categoryt enum declaration in src/alert.cpp doesn't take effect. It's not obvious to me why boost.python would be looking for such conversion given that the type is already defined/bound to python. Is it possible that you have another, old, version of the libtorrent python module installed that gets picked up instead? - Arvid Norberg.