On Wed, May 10, 2006 at 12:23:20PM +0200, Lars Gullik Bjønnes wrote:
> | Not bad.
> |
> | Btw I remember that concatenation all mathed/*.C into a single
> | translation unit and compiling this was several times faster
> | (I seem to remember 'four times') than compiling the small
> | chunks we hav
Abdelrazak Younes a écrit :
Bo Peng a écrit :
Dear list,
*Please* just put cold comparison data in this thread. No discussion
and debates. (Open another thread if needed).
On my dual processor Xeon 2.8G Linux workstation, I get
scons --config=force -j3 frontend=qt4 qt_dir=/path/to/qt4 =
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Mon, May 08, 2006 at 04:35:01PM -0500, Bo Peng wrote:
| > Dear list,
| >
| > *Please* just put cold comparison data in this thread. No discussion
| > and debates. (Open another thread if needed).
| >
| > On my dual processor Xeon 2.8G Linux workstat
Bo Peng a écrit :
BTW, I am really happy about the cygwin build, giving all the
difficulties in setting up a mingw build (Abdel, what do you think?
Will win/mingw be easier with scons?),
Yes, I think that's the case. And it's definitely faster on my machine.
Abdel.
Enrico Forestieri a écrit :
On Tue, May 09, 2006 at 06:24:42PM +0200, Abdelrazak Younes wrote:
Bo Peng a écrit :
Dear list,
*Please* just put cold comparison data in this thread. No discussion
and debates. (Open another thread if needed).
On my dual processor Xeon 2.8G Linux workstation, I ge
Please, attached find a patch fixing compilation with aiksaurus
and some other small thing.
All look reasonable. Will be applied.
Please, have a look at version.C.in as there are a couple of strings
("@PACKAGE_VERSION@" and "@VERSION_INFO@") that are not substituted
when generating version.C.
On Tue, May 09, 2006 at 04:44:47PM -0500, Bo Peng wrote:
> Now, I think I can claim that scons is *basically* working. It is
> already a straight 'scons' for linux, mingw and cygwin.
And now solaris, too. I start liking this scons thing ;-)
Please, attached find a patch fixing compilation with a
On Tue, May 09, 2006 at 04:44:47PM -0500, Bo Peng wrote:
> >Hmmm... I blindly applied my patch over your new commit without
> >reading it. Please, note the "appnend" typo.
>
> Yes. That is a ugly one. I will fix that one with others.
Ok, Thanks.
> Now, I think I can claim that scons is *basicall
On Tue, May 09, 2006 at 02:59:38PM -0500, Bo Peng wrote:
> spell checker and aikasurus are
> supposed to work now.
The spell checker works, but, although the Aiksaurus library is
indeed linked in, I am missing the Thesaurus entry in the Tools
menu.
Many things should still be tuned, among them:
Hmmm... I blindly applied my patch over your new commit without
reading it. Please, note the "appnend" typo.
Yes. That is a ugly one. I will fix that one with others.
Now, I think I can claim that scons is *basically* working. It is
already a straight 'scons' for linux, mingw and cygwin. The co
On Tue, May 09, 2006 at 10:57:29PM +0200, Enrico Forestieri wrote:
> I had just compiled successfully with aspell support when I saw your
> new commit. I still think that the attached patch is necessary.
Hmmm... I blindly applied my patch over your new commit without
reading it. Please, note the
On Tue, May 09, 2006 at 02:59:38PM -0500, Bo Peng wrote:
> >And you compiled using -O2 with scons, too, right? Otherwise this is
> >an unfair comparison. I have numbers close to yours on cygwin, but I
> >cannot convince scons to compile using -O2.
>
> With scons CCFLAGS=-O2, the compile time are a
The second column is bad. Developers certainly spend more time
on near 'null-builds' than on full rebuilds.
I agree. I have posted an email to the scons-list. Let us see what
they think about it.
Cheers,
Bo
On Tue, May 09, 2006 at 12:48:16PM +0200, Lars Gullik Bjønnes wrote:
> "Bo Peng" <[EMAIL PROTECTED]> writes:
>
> | Dear list,
> |
> | *Please* just put cold comparison data in this thread. No discussion
> | and debates. (Open another thread if needed).
> |
> | On my dual processor Xeon 2.8G Linu
On Mon, May 08, 2006 at 04:35:01PM -0500, Bo Peng wrote:
> Dear list,
>
> *Please* just put cold comparison data in this thread. No discussion
> and debates. (Open another thread if needed).
>
> On my dual processor Xeon 2.8G Linux workstation, I get
>
> scons --config=force -j3 frontend=qt4 qt_
And you compiled using -O2 with scons, too, right? Otherwise this is
an unfair comparison. I have numbers close to yours on cygwin, but I
cannot convince scons to compile using -O2.
With scons CCFLAGS=-O2, the compile time are about the same. This is
not surprising since the core command g++ tak
On Tue, May 09, 2006 at 06:24:42PM +0200, Abdelrazak Younes wrote:
> Bo Peng a écrit :
> >Dear list,
> >
> >*Please* just put cold comparison data in this thread. No discussion
> >and debates. (Open another thread if needed).
> >
> >On my dual processor Xeon 2.8G Linux workstation, I get
> >
> >sco
Abdelrazak Younes a écrit :
Bo Peng a écrit :
Dear list,
*Please* just put cold comparison data in this thread. No discussion
and debates. (Open another thread if needed).
On my dual processor Xeon 2.8G Linux workstation, I get
scons --config=force -j3 frontend=qt4 qt_dir=/path/to/qt4 =
Bo Peng a écrit :
Dear list,
*Please* just put cold comparison data in this thread. No discussion
and debates. (Open another thread if needed).
On my dual processor Xeon 2.8G Linux workstation, I get
scons --config=force -j3 frontend=qt4 qt_dir=/path/to/qt4 => 6:37s
autogen.sh; ./configu
"Bo Peng" <[EMAIL PROTECTED]> writes:
| Dear list,
|
| *Please* just put cold comparison data in this thread. No discussion
| and debates. (Open another thread if needed).
|
| On my dual processor Xeon 2.8G Linux workstation, I get
|
| scons --config=force -j3 frontend=qt4 qt_dir=/path/to/qt4
Dear list,
*Please* just put cold comparison data in this thread. No discussion
and debates. (Open another thread if needed).
On my dual processor Xeon 2.8G Linux workstation, I get
scons --config=force -j3 frontend=qt4 qt_dir=/path/to/qt4 => 6:37s
autogen.sh; ./configure; make -j3
21 matches
Mail list logo