Re: Newest Commit Could be improved

[Jackie Gleason]

No I added the MAKE variable and pointed to where the gnustep-config was, the point being I needed to point it at the GNUStep Make created with the android GCC compiler as opposed to the one from the linux compiler. Meaning if you are cross compiling you need a way to point at the other gnustep make.

That doesn't sound clear so let me know where I can expand.

Jackie

On Thu, Dec 8, 2011 at 1:03 PM, Ivan Vučica <address@hidden> wrote:

I suspect no. $MAKE does not contain the path to the program called "gnustep-config". 

Also, you can use the same "make" program for different platforms.

On Thu, Dec 8, 2011 at 03:24, Jackie Gleason <address@hidden> wrote:

The one of the last commits added the following to the configure...

MAKECC=`gnustep-config --variable=CC`

if test "$CC" != "$MAKECC"; then

  { { $as_echo "$as_me:$LINENO: error: You are running configure with the compiler ($CC) set to a different value from that used by gnustep-make ($MAKECC).  Please run configure again with your environment set to match your gnustep-make" >&5

$as_echo "$as_me: error: You are running configure with the compiler ($CC) set to a different value from that used by gnustep-make ($MAKECC).  Please run configure again with your environment set to match your gnustep-make" >&2;}

   { (exit 1); exit 1; }; }

  exit 1

fi 

Shouldn't this be changed to ...

MAKECC=`$MAKE/gnustep-config --variable=CC`

So if I am cross compiling I can use the MAKE variable to specify where the gnustep-make is? My case is that I am compiling for Android ARM using a Ubuntu x64 machine

_______________________________________________
Gnustep-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/gnustep-dev

--
Ivan Vučica - address@hidden