This issue arises because Xcode is not able to find the standard header files in its search path. These header files are usually obtained when GCC compiler is installed on the system.
Starting with Xcode 4.3, Command Line Tools must be manually installed to obtain GCC, LLVM compilers and MAKE utility. Please note that Command Line Tools requires Mac OS X 10.7.3 or later.
To install Command Line Tools, go to
Xcode>Preferences>Downloads>Command Line Tools>Install.
Further, the Command Line Tools do not install any SDKs. Therefore, when Simulink Coder references SDKs, it fails because it is unable to locate any header files. This can be resolved by allowing Simulink Coder to use the headers installed with Command Line Tools by removing references to SDKs that existed in previous versions of Xcode.
In the specific case of using MAC OS 10.7.x with Xcode 4.3 it is possible to remove the lines that refer to SDKROOT or MACOSX_DEPLOYMENT_TARGET from the “unixtools.mk” file if the file matches the use-case here. “unixtools.mk” is located at:
([matlabroot,'\rtw\c\tools\unixtools.mk'])
The references to SDKROOT and MACOSX_DEPLOYMENT_TARGET can be eliminated by removing the six lines that start with “%”s from the section of “unixtools.mk” I have included bellow:
ifeq ($(COMPUTER),MACI64)
DEFAULT_OPT_OPTS = -O0 -ffloat-store
- architecture support x86_64
ARCHS = x86_64
LD_NAMESPACE = -twolevel_namespace
LD_UNDEFS = -undefined error
% SDKROOT = /Developer/SDKs/MacOSX10.6.sdk
% MACOSX_DEPLOYMENT_TARGET = 10.5
CC = gcc -arch $(ARCHS)
CPP = g++ -arch $(ARCHS)
ANSI_OPTS = \
% -isysroot $(SDKROOT) \
% -mmacosx-version-min=$(MACOSX_DEPLOYMENT_TARGET) \
-fno-common -no-cpp-precomp -fexceptions
#instead of using -bundle, use -dynamiclib flag to make the lib dlopen compatible
SHRLIBLDFLAGS = \
-dynamiclib \
% -Wl,-syslibroot,$(SDKROOT) \
% -mmacosx-version-min=$(MACOSX_DEPLOYMENT_TARGET) \
-Wl,$(LD_NAMESPACE) $(LD_UNDEFS) -Wl,-exported_symbols_list,
endif
Lastly, spaces on the path are not supported on non-Windows machines. It is due to difficulties associated with make files (3rd party make tools) that have paths containing spaces, not MathWorks software. On Windows machines, the constraint is resolved by using short pathnames, but these are not available on non-Windows machines. So, also verify whether there are any spaces in the folder location from where the code generation and build is happening. Moving to a location without spaces has been seen to resolve the issue in few cases.
