Currently Being ModeratedMay 6, 2012 5:35 PM (in response to xnav)
Thanks for the response. Yes, that's how I started. I have now managed to get it to build static libraries; the piece I was missing was the scheme stuff. I also tried to build dynamic libraries, but still no luck with those. It was a little confusing because sometimes if I started a new project the scheme would allow me to create output as is; other times I had to edit the scheme first. So reading the documentation appears to have paid off after all.
FWIW, what I was trying to build was a missing library needed for a project in Python. The entire project has two C libraries, which I've managed to build now, altough I don't know if there are some specific options that I need to set for them to work with the C wrapper. The C wrapper is written in Cython, which creates a C file from Python-like statements. The end result of linking the two libraries and the compiled C wrapper should be a file that can be imported into Python, which should have an extension of ".so".
So far the last part is not working, so I don't know if the problem is with the build settings for the libraries, or something else.
Currently Being ModeratedMay 6, 2012 8:10 PM (in response to Resn8tor)
What is "the last part"? Building a ".so" library? That is for Linux. Mac shared libraries are ".dylib" files. Python includes tools to help you build extensions. The only part of Xcode you really need are the command line tools. Install those and then follow standard Python documentation for extensions.
Currently Being ModeratedMay 8, 2012 1:25 PM (in response to etresoft)
Python uses the .so extension for precompiled modules on the Mac. The build consists of converting the Cython source to C file, compiling the C file and linking it to two static libraries, libportmidi.a and libporttime.a, to create portmidi.so.