gnustep/tools-make
0
0
Fork 0
mirror of https://github.com/gnustep/tools-make.git synced 2025-04-23 22:33:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

When checking for an ObjC++ compiler in gnustep-make, try compiling - but not linking or executing.

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/tools/make/trunk@32817 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
Nicola Pero 2011-04-09 11:54:17 +00:00
parent cd36bb5890
commit 94dd631867
3 changed files with 2593 additions and 3360 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
ChangeLog
View file

@ -1,3 +1,9 @@
2011-04-09 Nicola Pero <nicola.pero@meta-innovation.com>
* configure.ac: Use AC_COMPILE_IFELSE instead of AC_TRY_IFELSE
when checking for ObjC++ support in the compiler.
* configure: Updated comments.
2011-04-09 Nicola Pero <nicola.pero@meta-innovation.com>
Use 'make check GNUSTEP_TEST_OBJCXX=yes' to enable ObjC++

5924
configure vendored
View file

File diff suppressed because it is too large Load diff

23
configure.ac
View file

@ -24,6 +24,21 @@ AC_INIT
AC_PREREQ(2.57)
AC_CONFIG_SRCDIR([application.make])
#
# TODO: This configure file should not contain any checks that depend on the
# Objective-C runtime being used or available. This is because on
# some platforms the Objective-C runtime itself is compiled using
# gnustep-make!
#
# All the runtime-dependent checks should go in gnustep-base.
#
# We still need compiler checks, because if we are compiling the
# Objective-C runtime itself, we need to know what compiler we have
# and what flags we can use. But these checks should test
# compilation, not linking or execution, because we don't necessarily
# have an Objective-C runtime available yet.
#
#--------------------------------------------------------------------
# Setup the library combination
#--------------------------------------------------------------------
@ -302,12 +317,6 @@ AC_SUBST(GNUSTEP_MAKE_STRICT_V2_MODE)
# Determine filesystem layout to use
#-------------------------------------------------------------------
# Hmmm - currently we only allow them to specify a file containing the
# filesystem layout. We could have a separate flag for each of the
# layout variables; that would be a lot of flags though! But maybe
# for completeness we could go through all of them and add a flag for
# each.
AC_MSG_CHECKING([for GNUstep filesystem layout to use])
AC_ARG_WITH(layout,[
--with-layout=FILE
@ -1264,7 +1273,7 @@ CXXFLAGS="$CXXFLAGS -x objective-c++"
CXXPPFLAGS_saved="$CXXPPFLAGS"
CXXPPFLAGS="$CXXPPFLAGS -x objective-c++"
AC_RUN_IFELSE([[
AC_COMPILE_IFELSE([[
@interface ObjCClass
{