Re: PicoGUI1 and 2

Frederic Wagner <[email protected]>
Newsgroups gmane.comp.video.picogui.devel
Message-ID <[email protected]>
On Thu, Apr 17, 2003 at 03:38:52PM -0600, Micah Dowty wrote:

hi everyone,

> Well, I understand that at this time C++ is prohibitive in a lot of
> embedded devices. 

ok i'm going to put my 2 ounces of salt
<disclaimer>
remember these are only comments
i'm not taking part in the project right now, so since I don't code I
don't think I have any right to tell other people what they should do or
not.
</disclaimer>

just to say, i'm using picogui on my laptop: an 486 with 4m of ram

I don't know how much time it takes on it to compile a two lines hello
world in c++

I tried (g++2.95), and turned off the computer after more than 30hours
of waiting. So basically I won't be able to compile pgui in c++ directly
on my laptop.
 
> The gamble is whether in a year or two it still will
> be.

what is quite sure is that in a year or two i'll still have my laptop.

for me pgui is super usefull on old material, and software for old pcs
is what lacks in unix.

> If you think so, then I'll happily shelve my hopes of doing this in
> C++ to gain a little more portability.

an other important point may be the following:

http://www.suse.de/~bastian/Export/linking.txt

I've been interested with that stuff quite some time ago so I don't know
what has been done yet. I've heard the kde guys have a workaround using
kdeinit, and it seems gcc3.1 may handle the problem. 
But gcc3.1 is at least 1.5 times slower for compiling than 2.95 so I don't 
like the idea of using it on old hardware.

Wagner Frederic

-- 
-----------------------------------------------------------------------
Unix - where you can throw the manual on the keyboard and get a command


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.