Re: question to backend/gui guru...
Hi, On 12.09.2006, at 11:29, [EMAIL PROTECTED] wrote: Some of the classes i might use : (picked up from www.gnustep.org/resources/documentation/Developer/Gui/Reference/) NSColor* NSCursor NSEvent NSFileWrapper NSFont*, NSGlyph* NSImage* NSGraphicsContext NSOpenGL* NSResponder NSScreen NSSound At least NSResponder and NSEvent will be very useful. If you use SDL and its event handling then you don't need those classes as well as NSGraphicsContext , NSOpenGL* and friends. Also, how would you want to use NSFont* and NSGlyph* in an OpenGL context? I assume it is a lot easier to use SDL for all this stuff rather than tweaking gui to work w/ SDL. You are still able to use base, of course. I've done that myself. -Phil -- Philippe C.D. Robert http://www.nice.ch/~phip ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Debug as default...
On Sep 20, 2006, at 06:19, Nicola Pero wrote: Anyway, let me know if '-g -O2' causes problems, I presume if the '- O2' seriously confuse the debugger let me know and we can revert that change, or maybe use '-g -O' ? At least the exception handling in libFoundation (which uses nested functions) is b0rked with -O2. Not sure about -O. Which is why we always disable it ... (is it possibly to filter out the -O per file?, eg MyStream_OPTIMIZE = no or something like this?) Greets, Helge -- Helge Hess http://docs.opengroupware.org/Members/helge/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Compiling and running a test tool
Hi, I can compile and run a test tool consisting of a single source file by invoking make test using a GNUmakefile like this include $(GNUSTEP_MAKEFILES)/common.make foo_OBJC_FILES=foo.m include $(GNUSTEP_MAKEFILES)/test-tool.make test: ./obj/foo which is pretty sweet. Trouble is, how do you extend this to a test tool which is spread over multiple source files? Or a test tool which depends on another tool build beforehand? The obvious thing to try was: thing_OBJC_FILES=foo.m bar.m include $(GNUSTEP_MAKEFILES)/test-tool.make test: ./obj/thing but that doesn't work at all. Changing that depends to test: thing means it will all compile and link sweetly but won't be run. It's getting late and my brain is slow. Help anyone? Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Compiling and running a test tool
Doh! Sorry to reply to my own post. Sorry to post in the first place. It is late and my brain is slow. I've sorted it now. *mutters about TABs in makefiles* Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep Testfarm Results
On Sep 20, 2006, at 5:25 AM, Nicola Pero wrote: Success Compile i386-unknown-netbsdelf3.0 Wed Sep 20 03:56:58 CEST 2006 Fail Compile i686-pc-linux-gnu Tue Sep 19 22:23:54 CEST 2006 Success Compile powerpc-apple-darwin7.9.0 Wed Sep 20 03:14:48 MDT 2006 Fail Compile sparc-sun-solaris2.7 Wed Sep 20 01:54:59 EDT 2006 Success Compile x86_64-unknown-linux-gnu Wed Sep 20 04:06:41 BST 2006 It looks like a 40% failure rate ... is there anything we need to/can do ? Are we supposed to ignore the testfarm results for now ? The sparc failure was caused by a bug in the test script (triggered by a change in gnustep-make) - which occurred before it creates the log files. I'll fix that. I don't know why the i686 logs aren't being uploaded. I'll check if it's a test-script failure or perhaps there's just a problem on that machine uploading the file. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
RE: Compiling and running a test tool
Thanks ... a test-tool is exactly the same as a tool; the only difference is that 'make install' does nothing. :-) So it's standard stuff -- include $(GNUSTEP_MAKEFILES)/common.make TEST_TOOL_NAME = test test_OBJC_FILES = foo.m include $(GNUSTEP_MAKEFILES)/test-tool.make At which point, 'make' will compile the tool. Thanks PS: 'make test' will work too, gnustep-make will recognize 'test' as the name of one of the tools and will compile that one. -Original Message- From: Sheldon Gill [EMAIL PROTECTED] Sent: Wednesday, September 20, 2006 3:47 pm To: Developer GNUstep gnustep-dev@gnu.org Subject: Compiling and running a test tool Hi, I can compile and run a test tool consisting of a single source file by invoking make test using a GNUmakefile like this include $(GNUSTEP_MAKEFILES)/common.make foo_OBJC_FILES=foo.m include $(GNUSTEP_MAKEFILES)/test-tool.make test: ./obj/foo which is pretty sweet. Trouble is, how do you extend this to a test tool which is spread over multiple source files? Or a test tool which depends on another tool build beforehand? The obvious thing to try was: thing_OBJC_FILES=foo.m bar.m include $(GNUSTEP_MAKEFILES)/test-tool.make test: ./obj/thing but that doesn't work at all. Changing that depends to test: thing means it will all compile and link sweetly but won't be run. It's getting late and my brain is slow. Help anyone? Regards, Sheldon ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
