I just realized that by setting some flags in CMake, I overwrote the default settings for Visual C++ that control the choice of run-time library. (Note that libraries usually make calls to the C runtime library.) There are 4 choices: DLL vs static, and debug vs release. Currently, all the projects seem to be set to "static release", so if you link with a different flavor you will get some annoying messages from the linker. I think the run-time library choice should match the portmidi library, and I'll fix the CMake files to use c runtime libraries as follows:
portmidi-static (debug) -> static debug runtime library portmidi-static (release) -> static release runtime library portmidi-dynamic (debug) -> dll debug runtime library portmidi-dynamic (release) -> dll release runtime library It is not obvious this is the right way to go. Since the c runtime library is widely shared, it would not be a bad choice to always use a dll even for static portmidi libraries. Getting visualC libraries to all use matching runtime libraries is a huge pain; suggestions are welcome. -Roger _______________________________________________ media_api mailing list [email protected] http://lists.create.ucsb.edu/mailman/listinfo/media_api
