[Gnustep-cvs] GNUstep Testfarm Results

2005-08-27 Thread Adam Fedor
Test results for GNUstep as of Sat Aug 27 06:34:09 EDT 2005
If a particular system failed compilation, the logs for that system will
be placed at ftp://ftp.gnustep.org/pub/testfarm

If you would like to add your machine to this list, set up a cron job
(make sure you set up your PATH and other environment variables correctly)
to run the Startup/scripts/test-gnustep script (see the script comments 
for more info).

Success Compile i386-unknown-netbsdelf2.0.2 Sat Aug 27 03:58:30 CEST 2005
Success Compile powerpc-apple-darwin7.9.0 Sat Aug 27 03:21:20 MDT 2005
Fail Compile sparc-sun-solaris2.7 Sat Aug 27 01:54:30 EDT 2005




Re: PCH Support

2005-08-27 Thread Helge Hess

On 26. Aug 2005, at 16:46 Uhr, Nicola Pero wrote:
... just wanted to encourage you and say that this would be a  
fantastic

addition to gnustep-make! :-)


OK, the Linux/gcc4 issue isn't solved yet, but at least on OSX it  
works (almost) like a charm.


I've added PCH to SOPE 4.5 and it now compiles in ~8mins instead of  
~16mins on a PM G5, so it indeed gives a huge speed boost.



How to use
==

First you need to reconfigure/reinstall gstep-make with --enable-pch:

  ./configure --enable-pch 

In your projects you create a header file which contains all the  
files you usually want to include, in SOPE we already had such files  
called "common.h", eg:


  common.h:
  #import 
  #import 

After that you need to tell gstep-make about that file by adding a  
new variable:


  MyProject_PCH_FILE = common.h

Thats it. 'make clean all' and it should compile much faster.


Notes
=

- The common.h will be included in _every_ source file of the project  
at the very top (automagically using -include). This is sometimes  
confusing and can lead to bugs with non-PCH setups, but necessary to  
ensure that the PCH actually gets used.


- On the first 'make all' the PCH will be generated. Subsequent  
"touch *.m; make all" are marginally faster (for SOPE 4.5 with ~20  
PCH's this is no measurable difference)


- The PCH will NOT pick up changes automagically. So you should not  
add 'volatile' headers to the PCH or you might experience weird  
effects (old headers getting used). Don't know whether auto- 
dependencies help here, at least a .d file is generated.


- Do not use PCH if your project/subproject has just one or two  
files. Will gain you nothin' but wasted diskspace.


- Precompiled headers are quite big! For SOPE common.h around ~13MB  
each (~250MB for SOPE).


- I have the impression that PCH also increases Dual-CPU saturation  
on the G5 (w/o using -j), don't know why. Maybe because cpp=>cc1obj  
pipeline is multitasked and somehow better used.


- The newer Xcode's do something called shared PCH. Don't know how  
this works, I suppose they hash the header-file and only regenerate  
when they differ. Should save disk-space and some PCH generation time.



How to get it
=

My gstep-make branch is available at:

  http://svn.opengroupware.org/SOPE/trunk/gnustep-make

You can retrieve it as a patch to 1.11.0 using:

  svn diff http://svn.opengroupware.org/SOPE/vendor/gnustep-make/ 
1.11.0 \

   http://svn.opengroupware.org/SOPE/trunk/gnustep-make

Issues
==

I have one issue with subprojects, apparently they are run w/o a  
submake invocation and somehow pick up wrong PCH_FILEs. Nicola, maybe  
you can look into the changes and tell me what I did wrong? ;-)


Another minor issue the patch has is that the PCH must live in the  
same directory like the makefile - when I use $(notdir), the PCH  
compilation rule somehow doesn't get picked up (see comments in  
makefile). I failed to see why (Nicola again ;-)
Note: to see this behaviour your main project and your subproject  
need to use different PCH_FILE names (otherwise the subproject picks  
the one of the parent).


PCH in Sarge gcc4 doesn't work. I won't have the time to run through  
the full gcc bug-reporting procedure as outlined in:

  http://gcc.gnu.org/bugs.html
If someone would find the time to build/submit a testcase it would be  
excellent.



Greets,
  Helge

PS: ratmice: I think you saw no speed gain because you didn't use - 
include which you should to ensure that the PCH is actually used (the  
PCH MUST be the first included header).

--
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


Re: PCH Support

2005-08-27 Thread Matt Rice


> PS: ratmice: I think you saw no speed gain because
> you didn't use - 
> include which you should to ensure that the PCH is
> actually used (the  
> PCH MUST be the first included header).


of course i did.. 
line 20 and 29 of pch.diff

btw, a reference to: 
http://lists.gnu.org/archive/html/discuss-gnustep/2005-01/msg00150.html



__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


Re: PCH Support

2005-08-27 Thread Helge Hess

On Aug 27, 2005, at 20:22, Matt Rice wrote:

PS: ratmice: I think you saw no speed gain because
you didn't use -
include which you should to ensure that the PCH is
actually used (the
PCH MUST be the first included header).

of course i did..
line 20 and 29 of pch.diff


OK, was just a wild guess ;-) Then, I don't know why you didn't see a 
speedup. Its fairly huge over here.


Of course tests on Linux/ix86 are pending and it will be interesting to 
see whether it gives measurable speedup given that Linux/ix86 is 
already thrice as fast as my G5 over here.


Greets,
  Helge
--
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


[Gnustep-cvs] gnustep/core/back ChangeLog Headers/cairo/Cairo...

2005-08-27 Thread Fred Kiefer
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: Fred Kiefer <[EMAIL PROTECTED]> 05/08/28 00:48:13

Modified files:
core/back  : ChangeLog 
core/back/Headers/cairo: CairoFontInfo.h CairoSurface.h 
core/back/Source/cairo: CairoContext.m CairoFontInfo.m 
CairoGState.m CairoSurface.m 
XGCairoGlitzSurface.m XGCairoSurface.m 
XGCairoXImageSurface.m 

Log message:
Get cairo surfaces working for resized windows.

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/ChangeLog.diff?tr1=1.387&tr2=1.388&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Headers/cairo/CairoFontInfo.h.diff?tr1=1.4&tr2=1.5&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Headers/cairo/CairoSurface.h.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/CairoContext.m.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/CairoFontInfo.m.diff?tr1=1.5&tr2=1.6&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/CairoGState.m.diff?tr1=1.6&tr2=1.7&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/CairoSurface.m.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/XGCairoGlitzSurface.m.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/XGCairoSurface.m.diff?tr1=1.2&tr2=1.3&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/core/back/Source/cairo/XGCairoXImageSurface.m.diff?tr1=1.2&tr2=1.3&r1=text&r2=text





Cairo backend

2005-08-27 Thread Fred Kiefer
Some of you may have noticed that this week the release 1.0 of cairo has
been published. For quite some time GNUstep has had a backend based on
this graphics library. But this has always been incomplete and also
cairo has changed a lot over the months. In the last few weeks I cleaned
up the code for this backend and extended it a bit. Basically it is now
ready to try it, although many features are still missing.

Known limitations:
- fonts are still hard coded
- text in NSTextView sometimes doesn't get displayed
- images are often displayed incorrect
- copying from one GState to another uses wrong transformation
- some minor operations are missing or untested

I hope to solve these problems within the next month and will make a
public announcment for the cairo backend after that. If you find other
bugs, feel free to report them, or even better help to resolve them.

If you want to compile the cairo backend, use the command:

./configure --enable-graphics=cairo --disable-glitz

We probably should switch glitz off by default, as this is not offically
supported by cairo at the moment

Cheers
Fred


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


Re: Cairo backend

2005-08-27 Thread Nicolas Roard
On 8/28/05, Fred Kiefer <[EMAIL PROTECTED]> wrote:
> Some of you may have noticed that this week the release 1.0 of cairo has
> been published. For quite some time GNUstep has had a backend based on
> this graphics library. But this has always been incomplete and also
> cairo has changed a lot over the months. In the last few weeks I cleaned
> up the code for this backend and extended it a bit. Basically it is now
> ready to try it, although many features are still missing.

Wow, excellent news !

> Known limitations:
> - fonts are still hard coded
> - text in NSTextView sometimes doesn't get displayed
> - images are often displayed incorrect
> - copying from one GState to another uses wrong transformation
> - some minor operations are missing or untested
> 
> I hope to solve these problems within the next month and will make a
> public announcment for the cairo backend after that. If you find other
> bugs, feel free to report them, or even better help to resolve them.

I'll try to install cairo and test that :-)

thanks,

-- 
Nicolas Roard
"Any sufficiently advanced technology is indistinguishable from magic."
  -Arthur C. Clarke


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


[Gnustep-cvs] gnustep/Startup ChangeLog ErrorList InstallGNUs...

2005-08-27 Thread Adam Fedor
CVSROOT:/cvsroot/gnustep
Module name:gnustep
Branch: 
Changes by: Adam Fedor <[EMAIL PROTECTED]>  05/08/28 01:47:15

Modified files:
Startup: ChangeLog ErrorList InstallGNUstep configure 
 configure.ac 
Startup/scripts: test-gnustep 

Log message:
* InstallGNUstep: All extern package configuration
* configure.ac: Allow disable-xml, warn on missing libobjc
* scripts/test-gnustep: Remove GS_CONFIG_OPTIONS

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/ChangeLog.diff?tr1=1.38&tr2=1.39&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/ErrorList.diff?tr1=1.11&tr2=1.12&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/InstallGNUstep.diff?tr1=1.28&tr2=1.29&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/configure.diff?tr1=1.24&tr2=1.25&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/configure.ac.diff?tr1=1.24&tr2=1.25&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gnustep/gnustep/Startup/scripts/test-gnustep.diff?tr1=1.4&tr2=1.5&r1=text&r2=text