• Gian Perrone (31/31) Sep 17 2009 I just wanted you to know that i built dwt-linux (from the repository)
• Frank Benoit (1/1) Sep 17 2009 Thats good news. How long was the compile time? How big the executable?
• Gian Perrone (11/12) Sep 17 2009 real 9m16.925s
• Spacen Jasset (3/19) Oct 11 2009 How come the user time is more than the real time? Is the real time not
• =?ISO-8859-1?Q?=22J=E9r=F4me_M=2E_Berger=22?= (13/33) Oct 11 2009 H,=20
• digited (9/19) Oct 18 2009 Thanks for the patch!
• digited (2/3) Oct 18 2009 p.s. building takes 3m 51sec on a single 2GHz core
• Frank Benoit (4/30) Oct 19 2009 I know this warning. I do not remember what the solution was, to make it

Gian Perrone <gperrone gmx.de> writes:

I just wanted you to know that i built dwt-linux (from the repository) 
with ldc, just a few small changes were made:

hg diff -U0

diff -r 5f6d9bb33a53 dsss.conf
--- a/dsss.conf Sat Apr 04 21:38:37 2009 +0200
+++ b/dsss.conf Thu Sep 17 16:19:06 2009 +0200
   -3,1 +3,1   
-buildflags+=-Jres
+buildflags+=-Jres -version=TANGOSVN
diff -r 5f6d9bb33a53 dwt/dwthelper/utils.d
--- a/dwt/dwthelper/utils.d     Sat Apr 04 21:38:37 2009 +0200
+++ b/dwt/dwthelper/utils.d     Thu Sep 17 16:19:06 2009 +0200
   -488,1 +488,1   
-//alias tango.text.convert.Utf.toString16 toString16;
+alias tango.text.convert.Utf.toString16 toString16;
diff -r 5f6d9bb33a53 dwt/internal/cairo/Cairo.d
--- a/dwt/internal/cairo/Cairo.d        Sat Apr 04 21:38:37 2009 +0200
+++ b/dwt/internal/cairo/Cairo.d        Thu Sep 17 16:19:06 2009 +0200
   -79,1 +79,1   
-    mixin("public static R " ~ NameOfFunc!(cFunc) ~ "( P p ){
+    mixin("public static extern(C) R " ~ NameOfFunc!(cFunc) ~ "( P p ){
diff -r 5f6d9bb33a53 dwt/internal/gtk/OS.d
--- a/dwt/internal/gtk/OS.d     Sat Apr 04 21:38:37 2009 +0200
+++ b/dwt/internal/gtk/OS.d     Thu Sep 17 16:19:06 2009 +0200
   -637,1 +637,1   
-    mixin("public static R " ~ NameOfFunc!(cFunc) ~ "( P p ){
+    mixin("public static extern(C) R " ~ NameOfFunc!(cFunc) ~ "( P p ){

The browser widget had to be ignored (move away dwt/browser and 
dwt/internals/mozilla). The "simple" example was run successfully, i 
didn't test more.

dwt-addons doesn't work because of a bug with tuples in ldc.

Frank Benoit <keinfarbton googlemail.com> writes:

Thats good news. How long was the compile time? How big the executable?

Gian Perrone <gperrone gmx.de> writes:

Frank Benoit schrieb:
 Thats good news. How long was the compile time? How big the executable?

real 9m16.925s
user 67m34.623s
sys 4m28.682s

That was on a dual Xeon quad core platform (= 8 cores) 2.5GHz via SSH, 
because on my laptop it was way to slow to repeat changing one code line 
and compiling again.

I remember compiling DWT 3.4-1 on my dual-core laptop with an old dmd 
version in 6 seconds.

libDO-dwt.a is just 279M (remember, w/o browser and internals.mozilla) 
and simple just 11M...

Spacen Jasset <spacenjasset yahoo.co.uk> writes:

Gian Perrone wrote:
 Frank Benoit schrieb:
 Thats good news. How long was the compile time? How big the executable?

 
 real 9m16.925s
 user 67m34.623s
 sys 4m28.682s
 
 That was on a dual Xeon quad core platform (= 8 cores) 2.5GHz via SSH, 
 because on my laptop it was way to slow to repeat changing one code line 
 and compiling again.
 
 I remember compiling DWT 3.4-1 on my dual-core laptop with an old dmd 
 version in 6 seconds.
 
 libDO-dwt.a is just 279M (remember, w/o browser and internals.mozilla) 
 and simple just 11M...

How come the user time is more than the real time? Is the real time not 
the wall clock difference?

=?ISO-8859-1?Q?=22J=E9r=F4me_M=2E_Berger=22?= <jeberger free.fr> writes:

Spacen Jasset wrote:
 Gian Perrone wrote:
 Frank Benoit schrieb:
 Thats good news. How long was the compile time? How big the executabl=



e?
 real 9m16.925s
 user 67m34.623s
 sys 4m28.682s

 That was on a dual Xeon quad core platform (=3D 8 cores) 2.5GHz via SS=


H,=20
 because on my laptop it was way to slow to repeat changing one code=20
 line and compiling again.

 I remember compiling DWT 3.4-1 on my dual-core laptop with an old dmd =


 version in 6 seconds.

 libDO-dwt.a is just 279M (remember, w/o browser and internals.mozilla)=


=20
 and simple just 11M...

=20
 How come the user time is more than the real time? Is the real time not=

=20
 the wall clock difference?

	Yes, but the user time is the time spent in user code on each CPU=20
or Core. So if you spend 1min at 100% on two cores, you get 2min of=20
user time and 1min of real time.

		Jerome
--=20
mailto:jeberger free.fr
http://jeberger.free.fr
Jabber: jeberger jabber.fr

digited <digited yandex.ru> writes:

Gian Perrone Wrote:

 I just wanted you to know that i built dwt-linux (from the repository) 
 with ldc, just a few small changes were made:
 
 <...patch here...>
 
 The browser widget had to be ignored (move away dwt/browser and 
 dwt/internals/mozilla). The "simple" example was run successfully, i 
 didn't test more.
 
 dwt-addons doesn't work because of a bug with tuples in ldc.

Thanks for the patch!

I've compiled some HelloWorlds with LDC trunk, Tango trunk and xfbuild on
openSUSE 11.1 x86_64:

xfbuild dwt-samples/examples/helloworld/HelloWorld1.d -Idwt-linux
-Jdwt-linux/res -d-version=TANGOSVN -d +ohw1 -L-lz -L-lgtk-x11-2.0
-L-lgdk-x11-2.0 -L-latk-1.0 -L-lgdk_pixbuf-2.0 -L-lgthread-2.0
-L-lpangocairo-1.0 -L-lfontconfig -L-lXtst -L-lXext -L-lXrender -L-lXinerama
-L-lXi -L-lXrandr -L-lXcursor -L-lX11 -L-lXfixes -L-lpango-1.0 -L-lgobject-2.0
-L-lgmodule-2.0 -L-ldl -L-lglib-2.0 -L-lcairo

However, i have problems with Gtk/Gdk and locale - when i try to run a DWT app,
i get:

(process:9804): Gdk-WARNING **: locale not supported by C library
(process:9804): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

And the app halts without showing any window. 'locale' returns en_US.UTF-8
everywhere, resetting it with 'localedef' also doesn't change the error. May it
be some DWT bug?

digited <digited yandex.ru> writes:

digited Wrote:

 xfbuild dwt-samples/examples/helloworld/HelloWorld1.d -Idwt-linux
-Jdwt-linux/res -d-version=TANGOSVN -d +ohw1 -L-lz -L-lgtk-x11-2.0
-L-lgdk-x11-2.0 -L-latk-1.0 -L-lgdk_pixbuf-2.0 -L-lgthread-2.0
-L-lpangocairo-1.0 -L-lfontconfig -L-lXtst -L-lXext -L-lXrender -L-lXinerama
-L-lXi -L-lXrandr -L-lXcursor -L-lX11 -L-lXfixes -L-lpango-1.0 -L-lgobject-2.0
-L-lgmodule-2.0 -L-ldl -L-lglib-2.0 -L-lcairo

p.s. building takes 3m 51sec on a single 2GHz core

Frank Benoit <keinfarbton googlemail.com> writes:

digited schrieb:
 Gian Perrone Wrote:
 
 I just wanted you to know that i built dwt-linux (from the repository) 
 with ldc, just a few small changes were made:

 <...patch here...>

 The browser widget had to be ignored (move away dwt/browser and 
 dwt/internals/mozilla). The "simple" example was run successfully, i 
 didn't test more.

 dwt-addons doesn't work because of a bug with tuples in ldc.

 
 Thanks for the patch!
 
 I've compiled some HelloWorlds with LDC trunk, Tango trunk and xfbuild on
openSUSE 11.1 x86_64:
 
 xfbuild dwt-samples/examples/helloworld/HelloWorld1.d -Idwt-linux
-Jdwt-linux/res -d-version=TANGOSVN -d +ohw1 -L-lz -L-lgtk-x11-2.0
-L-lgdk-x11-2.0 -L-latk-1.0 -L-lgdk_pixbuf-2.0 -L-lgthread-2.0
-L-lpangocairo-1.0 -L-lfontconfig -L-lXtst -L-lXext -L-lXrender -L-lXinerama
-L-lXi -L-lXrandr -L-lXcursor -L-lX11 -L-lXfixes -L-lpango-1.0 -L-lgobject-2.0
-L-lgmodule-2.0 -L-ldl -L-lglib-2.0 -L-lcairo
 
 However, i have problems with Gtk/Gdk and locale - when i try to run a DWT
app, i get:
 
 (process:9804): Gdk-WARNING **: locale not supported by C library
 (process:9804): Gtk-WARNING **: Locale not supported by C library.
 Using the fallback 'C' locale.
 
 And the app halts without showing any window. 'locale' returns en_US.UTF-8
everywhere, resetting it with 'localedef' also doesn't change the error. May it
be some DWT bug?

I know this warning. I do not remember what the solution was, to make it
go away, but my application always worked with it.
So the not showing window or halt might not be related to the warning.