Chris Rolfe

I wanted to share a solution/workaround for noisy Xcode warnings... 

Importing Max C headers under the Max 8 SDK projects w/ Catalina and Xcode 11.4 generates a distracting number of compiler warnings:

20 x "This function declaration is not a prototype"

There's a clang pragma to suppress the warning. Wrap any Max header #include statements in main.c with the "-Wstrict-prototypes" option ignored:

// ignore C function prototype warnings
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Wstrict-prototypes"
#include "ext.h"
#include "ext_obex.h"
#include "z_dsp.h"
#pragma clang diagnostic pop

One warning left: "Traditional headermap style is no longer supported." can be fixed by changing the project build setting:

"Always Search User Paths (Deprecated)" = NO // was: YES

If anyone spots something dubious, kindly post a note in this thread. Or perhaps the prototype warnings could be suppressed within the build .config file? I don't like to change the library source files though.

I wanted to share a solution/workaround for noisy Xcode warnings... 
 
Importing Max C headers under the Max 8 SDK projects w/ Catalina and Xcode 11.4 generates a distracting number of compiler warnings: 

20 x "This function declaration is not a prototype" 

There's a clang pragma to suppress the warning. Wrap any Max header #include statements in main.c with the "-Wstrict-prototypes" option ignored: 


One warning left: "Traditional headermap style is no longer supported."  can be fixed by changing the project build setting: 

Search paths: 
"Always Search User Paths (Deprecated)" = NO                  // was: YES

If anyone spots something dubious, kindly post a note in this thread. Or perhaps the prototype warnings could be suppressed within the build .config file?  I don't like to change the library source files though. 

I wanted to share a solution/workaround for noisy Xcode warnings... 
 
Importing Max C headers under the Max 8 SDK projects w/ Catalina and 

xcode-11-4-and-max-8-sdk-project-settings-in-c

In my experience, you can let Xcode fix "This function declaration is not a prototype" with its "Fix this" feature and all will be well. Is there any reason to avoid letting Xcode make the automatic fix?

Alternately, you can just disable Strict Prototypes in Build Settings

re: "fix this" started offered to change Cycling74's headers.

Changing strict protype=no in XCode's build settings is equivalent the clang pragma(s).

re: "fix this" started offered to change Cycling74's headers. 

Xcode 11.4 and Max 8 SDK Project settings in C