> Inside a GNUmakefile, that variable is always set - in both gnustep-make v1 > and v2. > > Outside a GNUmakefile (eg, in a configure script), it is set in gnustep-make > v1, > but not in gnustep-make v2. In gnustep-make v2 you can still get the value > of that variable by executing > > gnustep-config --variable=GNUSTEP_HOST_CPU > > the gnustep-config script should always be in your PATH if gnustep-make v2 > was installed correctly.
PS: If you want to support cross-compilation, you may need to use the GNUSTEP_TARGET_CPU variable instead. That's quite easy. The variable is defined inside a GNUmakefile, in both v1 and v2. :-) Outside a GNUmakefile - eg, in a configure script - the variable should be set to whatever --target=TARGET was passed on the command-line (it's then the responsibility of whoever is compiling to pass the right one) or, if no --target= option was passed, to GNUSTEP_HOST_CPU, as determined using the gnustep-config script. :-) Thanks _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
