One thing failed: I cannot cross-compile libc++. This can be problematic on the final toolchain as Xcode defaults to it.
On Jun 17, 2013, at 11:32, Maxthon Chan <[email protected]> wrote: > Partial success: now I can get editing work on Xcode with all code completion > things. So the tasks coming now is to make sure it edits with Objective-C. > Cross-building will be a total different story as clearly OS X does not run > ELF and Xcode have guards against it. (However it does make it easier to > build projects sharing code between OS X and GNUstep, although some Makefiles > or tools are still called for.) > > If you use that kit, you will see traces hinting OS X 10.9 SDK - be calm, I > used modified files from OS X 10.9 SDK to make Xcode recognise this. No > actual OS X SDK file is included > > On Jun 17, 2013, at 9:54, Chan Maxthon <[email protected]> wrote: > >> How about use SenTestingKit and CXXTest? Since I am building cross tools to >> build GNUstep code targeting Linux on OS X for Xcode 4.6 and Xcode 5, those >> kits from 4.6 sounds reasonable to use for that purpose. >> >> 发自我的 iPad >> >> 在 2013-6-17，9:50，Stefan Bidi <[email protected]> 写道： >> >>> I'd like to extend gnustep-tests to be able to test .c and .cc files. The >>> obvious reason is because I'd like to be able to independently test >>> -corebase without having to link against against -base. >>> >>> I had took a peak into gnustep-tests.in and started preparing a patch. I >>> tried to create a patch but have not been successful in making it actually >>> work. To be honest, after a few hours of looking at the script, I haven't >>> been able to figure out exactly how it works. I figured the >>> run_test_file() and build_and_run() are the correct place to build c and >>> c++ files, so I extended these (instead of trying to screw around with the >>> GNUmakefile.in). Attached is my failed attempt at patching gnustep-tests. >>> >>> Could someone more familiar with the script give me some pointers to finish >>> the patch? I believe I'm 50% there already, but I just don't understand >>> enough of what is happening in gnustep-tests to take it the rest of the way. >>> >>> Stef >>> <gnustep-tests.patch> >>> _______________________________________________ >>> Gnustep-dev mailing list >>> [email protected] >>> https://lists.gnu.org/mailman/listinfo/gnustep-dev >> _______________________________________________ >> Gnustep-dev mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/gnustep-dev > > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev
_______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
