Then just do the 'npm install' or your python script again and everything is good. Then change the CXX environment variable to use it. To use it just build it with something like: The program basically patches the clang++ arguments on the fly to replace the -mmacosx-version-min=xxx parameter and writes a log of the environment and arguments to /tmp/vardump.txt I ran across this post when coming up with the solution. I ended up writing a program which allowed me to use the 3rd party nodes without patching them to fix this issue.
COMPILING CODE IN XCODE 10 UPDATE
I ran into a related program trying to update an old ionics-2 program which uses various node modules with alot of python scripts. Setup(cmdclass=, ext_modules=cythonize(ext_modules))
Here is my code setup.py if platform.system() = "Windows":Įxtra_args = Įxt_modules = [Extension("noway", compile_files,
COMPILING CODE IN XCODE 10 HOW TO
Had anyone have something similar? Any clues on how to deal with that?
It seems like anaconda uses libstdc++ instead of libc++ for Mac. My anaconda environment is this: Python 2.7.15 |Anaconda custom (64-bit)| (default, May 1 2018, 18:37:05) G++ -bundle -undefined dynamic_lookup -L/anaconda2/envs/python2.7-base/lib -arch x86_64 -arch x86_64 build/temp.macosx-10.6-x86_64-2.7/one.o build/temp.macosx-10.6-x86_64-2.7/noway.o -L/anaconda2/envs/python2.7-base/lib -o /Users/dkotsur/Projects/InCeM/IF-MedialAxis/test/noway.soĬlang: warning: libstdc++ is deprecated move to libc++ with a minimum deployment target of OS X 10.9 Ĭlang: error: linker command failed with exit code 1 (use -v to see invocation)Įrror: command 'g++' failed with exit status 1 I have tried to compile a simple example with Cython and got this linker error (macOS, Xcode 10): gcc -fno-strict-aliasing -I/anaconda2/envs/python2.7-base/include -arch x86_64 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I/anaconda2/envs/python2.7-base/include/python2.7 -c noway.cpp -o build/temp.macosx-10.6-x86_64-2.7/noway.o -std=c++11 -Os -stdlib=libc++ -mmacosx-version-min=10.7