Re: checking Mac OS X headers

[Vincent Torri]

Hey,

> > > > configure: error: in `/home/torri/svnroot/evas':
> > > > configure: error: Objective C preprocessor "/lib/cpp" fails sanity check
> > > >
> > > > I have looked at config.log but it does not help a lot.
> > >
> > > Will you allow us to have a look at it?
> > > (IOW, please post it.)
> >
> > I have attached it.
>
> Here's the clue:
>
> > configure:11850: checking whether we are using the GNU Objective C compiler
> > configure:11869: gcc -c   conftest.m >&5
> > gcc: error trying to exec 'cc1obj': execvp: No such file or directory
> > configure:11869: $? = 1
>
> Your compiler doesn't speak Objective C.  Solution is to install the
> respective frontend.

We have removed the support of mac os x but one of our devs wanted to 
compile the library, so i ask again. We currently have the following 
alternative

1) developpers who want to compile mac os x port can not because 
AC_LANG_PUSH/POP([Objective C]) is missing

2) developpers who have no mac os x (most of them), and certainly no objc 
gcc front end, must install it if we add AC_LANG_PUSH/POP([Objective C]), 
which is quite annoying.

is it possible, without having an objc compiler, to have that code:

AC_LANG_PUSH([Objective C])

AC_CHECK_HEADERS([/System/Library/Frameworks/Cocoa.framework/Headers/Cocoa.h],
   [
    have_dep="yes"
    evas_engine_[]$1[]_libs="-framework Cocoa"
   ],
   [have_dep="no"])

AC_LANG_POP([Objective C])

working ?

I can maybe execute that code if the host is darwin, but it is not the 
standard way of checking features, iirc

thank you

Vincent