Hello:
I tried using it for an embedded application using a coldfire 32-bit
processor chip.
The BIGGEST problem I faced was with the BOOST library.
The library itself needs to run with RTTI turned on and also with c++
exceptions turned on.
This alone would cause your application to be twice as big and run
half as fast.
Also support for not using the wide string (aka UNICODE) would also be
helpful.
So I abandoned using it for my embedded device.
It needs to get a little more mature before trying to port it to an
embedded device.
However, I have remained subscribed to this mailing list as I am
following the progress of the WT development.
It definitely needs a lot more work to run in an embedded environment.
Anyway, GOOD LUCK if you try to port it.
-- John Paul Giordano
________________________________
From: Andrii Arsirii [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 8:08 AM
To: [email protected]
Subject: [Wt-interest] Application size for embedded application
Hi, all.
I have positive experience in using witty.
Now I'm evaluating witty for use in embedded device project (web
configuration).
Product is a manufactured device with a flash memory running under
busybox (linux).
Current web-interface implementation uses GoAhead web server. It's a
terrible mix of shell, C, JavaScript, ASP, TCL.
C++ object-oriented implementation would be much easier to maintain.
Problem is that device has been designed to have only 4Mb of flash.
Current GoAhead interface (with full logic) fits in 300Kb (gzip).
I have tried to evaluate witty application size.
I've made empty application with wthttp connector on i386 arch.
Build options: MinSizeRel, -DHAVE_GNU_REGEX, -fvisibility=hidden,
without libz and OpenSSL, static linkage with wt and libstdc++,
stripping. WT version 2.1.5.
It has size of 680Kb (gzip).
[EMAIL PROTECTED]:~/GUI/app/build# ldd gui
linux-gate.so.1 => (0xb7fe2000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb7fb7000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0
(0xb7f9f000)
libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7e4f000)
/lib/ld-linux.so.2 (0xb7fe3000)
[EMAIL PROTECTED]:~/GUI/app/build# file gui
gui: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped
[EMAIL PROTECTED]:~/GUI/app/build# ls -la gui
-rwxr-xr-x 1 root root 1820520 2008-10-29 09:57 gui
[EMAIL PROTECTED]:~/GUI/app/build# gzip gui
[EMAIL PROTECTED]:~/GUI/app/build# ls -la gui.gz
-rwxr-xr-x 1 root root 684153 2008-10-29 09:57 gui.gz
[EMAIL PROTECTED]:~/GUI/app/build# upx gui
Ultimate Packer for eXecutables
Copyright (C)
1996,1997,1998,1999,2000,2001,2002,2003,2004,2005,2006,2007
UPX 3.01 Markus Oberhumer, Laszlo Molnar & John Reiser Jul 31st
2007
File size Ratio Format Name
-------------------- ------ ----------- -----------
1820520 -> 583056 32.03% linux/elf386 gui
Packed 1 file.
[EMAIL PROTECTED]:~/GUI/app/build# ls -la gui
-rwxr-xr-x 1 root root 583056 2008-10-29 09:57 gui
My company will continue investigation of witty in case if I get for
empty application at least the same size as GoAhead has.
So I have to fit in <300Kb for empty witty application with libstdc++
inlined (gzipped). Is that possible?
Company's about to begin mass production of devices and in case of
choosing witty you guys I guess will have a good contract :).
Can you advice something else to decrease application size?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
