Skip to content

OSX default build setup broken in clean environment #31

Open

Description

@RonstaMonsta

When running inside a clean, new virtualenv, setup.py fails to build the cython extensions for PyPylon.

(venv) ~/Work/Git/PyPylon$ python setup.py build
running build
running build_py
creating build
creating build/lib.macosx-10.12-x86_64-3.6
creating build/lib.macosx-10.12-x86_64-3.6/pypylon
copying pypylon/init.py -> build/lib.macosx-10.12-x86_64-3.6/pypylon
creating build/lib.macosx-10.12-x86_64-3.6/pypylon/cython
copying pypylon/cython/init.py -> build/lib.macosx-10.12-x86_64-3.6/pypylon/cython
running build_ext
cythoning cython/version.pyx to cython/version.cpp
building 'pypylon.cython.version' extension
creating build/temp.macosx-10.12-x86_64-3.6
creating build/temp.macosx-10.12-x86_64-3.6/cython
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -I/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers -I/Library/Frameworks/pylon.framework/Headers -I/Library/Frameworks/pylon.framework/Headers/GenICam -I/Users/rbendor/Work/Git/pynnacle/venv/lib/python3.6/site-packages/numpy/core/include -I/usr/local/Cellar/python3/3.6.2/Frameworks/Python.framework/Versions/3.6/include/python3.6m -c cython/version.cpp -o build/temp.macosx-10.12-x86_64-3.6/cython/version.o
cython/version.cpp:486:10: fatal error: 'pylon/PylonVersionNumber.h' file not found
#include "pylon/PylonVersionNumber.h"
^
1 error generated.
error: command 'clang' failed with exit status 1

Activity

  1. RonstaMonsta commented on Jul 24, 2017

    @RonstaMonsta
    Author

    After digging a little deeper, it looks like the issue comes from a missing compiler flag: the information to link with the pylon framework isn't there. Currently the header folders are added, but the structure of how the headers are stored inside the pylon framework doesnt match the expected format of 'pylon/foo.framework'.
    The option -F <path/to/pylon.framework> need to be added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions