It was built with the following compiler: Target: x86_64-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/opt/gcc/4.1.1 --enable-languages=c,c++,fortran,objc,obj-c++ --disable-checking --with-system-zlib --enable-shared --enable-__cxa_atexit x86_64-suse-linux Thread model: posix gcc version 4.1.1
Thanks, GJC -- Gregory Casamento ----- Original Message ---- From: Fred Kiefer <[EMAIL PROTECTED]> To: Xavier Glattard <[EMAIL PROTECTED]> Cc: gnustep-dev@gnu.org Sent: Monday, April 9, 2007 7:12:25 AM Subject: Re: NSAnimation... Xavier Glattard wrote: > Fred Kiefer <fredkiefer <at> gmx.de> writes: >> For me it looks even worse: >> >> Compiling file NSAnimation.m ... >> In file included from >> /usr/GNUstep/System/Library/Headers/GNUstepBase/GSIArray.h:138, > compilation twice now, with no luck. >>>> from NSAnimation.m:53: >> /usr/GNUstep/System/Library/Headers/GNUstepBase/GSUnion.h:112: error: >> conflicting types for ‘NSAnimationProgress’ >> ../Headers/AppKit/NSAnimation.h:164: error: previous declaration of >> ‘NSAnimationProgress’ was here > (...) > > Did you check out -base ? I made some changes in GSIArray.h > Yes, this was my fault, after recompiling base it worked fine. >> I currently don't have the time to look into this. Form a quick look it >> is rather a problem in GSIArray than in NSAnimation. But Xavier, when >> you fix it, could you please also move all the inline functions from the >> header to the implementation file? We don't want to clutter up the >> environment for all the users of this header file. > > Ok. I use these inline in the demo : i will move them in a private > header... > Great. >> Could you please also move over to GNUstep indentation and white space >> rules? It is not too hard you just need to get used to it. > > Is that so important ?? It actually looks pretty ;-) > I will do my best. > Let's not start to discuss this. We all hate part of the rules, but we could never agree on any others and it really is best to have one set of formatting standards. I am also on the cairo mailing list and there the rules for code are even stricter then ours (totally different too, of course), but everybody keeps with them. Cheers, Fred _______________________________________________ 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