OK, I have tried it and here are some numbers.
make clean all (in gtkhtml HEAD)
1rst run:
real9m5.642s
user6m4.560s
sys 1m57.260s
2nd run:
real3m54.688s
user1m58.910s
sys 1m42.050s
ccache -s
cache hit
I have not tried this, your mileage may vary, but...
http://ccache.samba.org/ has a "compiler cache" program that recognizes
when recompiling a file will generate the same output as last time and
avoids recompiling it. Supposed to speed up recompiles when the source
hasn't changed much (eg, if yo
Anders Carlsson started a stickynotes component at one point, in
evolution/notes. I don't know how complete it was, and even the parts
that were done probably don't match the current APIs any more. But it
might be worth looking at.
-- Dan
On Tue, 2002-05-07 at 09:33, James D Strandboge wrote:
>
On Tue, 2002-05-07 at 10:30, Ross Burton wrote:
> On Tue, 2002-05-07 at 14:48, Rodrigo Moya wrote:
> > you have to do an Evolution shell component, as is done in addressbook/,
> > mail/ and calendar/. For a simpler example, you should look at
> > shell/evolution-test-component.c, in the evolution
On Tue, 2002-05-07 at 14:48, Rodrigo Moya wrote:
> you have to do an Evolution shell component, as is done in addressbook/,
> mail/ and calendar/. For a simpler example, you should look at
> shell/evolution-test-component.c, in the evolution sources.
I tried coding a shell component recently but
On Tue, 2002-05-07 at 15:33, James D Strandboge wrote:
> I think evo is so cool, I wanted to help out. One thing a client of
> mine wants is a memos component so he can view memos sync'd with
> gnome-pilot in evolution.
>
> I looked around in the code and on the ximian site, but could not find
>
I think evo is so cool, I wanted to help out. One thing a client of
mine wants is a memos component so he can view memos sync'd with
gnome-pilot in evolution.
I looked around in the code and on the ximian site, but could not find
anything on 'getting started'. Any tips on what I should look at
On Tue, 2002-05-07 at 01:32, Not Zed wrote:
> Jeff is correct.
>
> You shouldn't lose any mail, but you might lose some flags or corrupt
> the indices or just make the two mailers thrash against each other.
> Making them multiprocess-writable would be a lot of work, even
> multiprocess one-write
I put in an old patch I wrote a while ago in my spare time, to update
and speed up camel-object a bit. You'll need to rebuild anything that
depends on camel as camel-object-class and camel-object have changed
size.
Any other code (outside of gnome cvs:/evolution) that uses it may need
some slig
