Re: EB-lite alpha released

Mathias <[email protected]>
Newsgroups gmane.network.everybuddy.user
Organization none
Message-ID <[email protected]>
Yes, its work but please check that eb ignore the
SIGPIPE from the sockets ;-)

Program received signal SIGPIPE, Broken pipe.
0x40141a24 in write () from /lib/libc.so.6

#0  0x40141a24 in write () from /lib/libc.so.6
#1  0x0000000c in ?? ()
#2  0x0804f631 in eb_gui_broadcast (command=0xbffff41c, num_params=4) at gui_comms.c:553
...

Best Regards

Mathias

On Tuesday 04 February 2003 18:13, Meredydd Luff wrote:
> Well, the subject says it all. Come and get it! Shortly, Rob will be
> uploading it to the website, but for now you can use my mirror, at:
>
> http://blackhole.wincoll.ac.uk/~meredydd/eb-lite/
>
> System requirements are: Qt 3.0 or greater; autotools (v1.4 works for me)
>
> It must be built from source - it's standard automake. However, it is in
> fact two separate applications - eb-lite (the core) and ebqt (the user
> interface). Each must be built separately, for example:
>
> $ tar -zxvf eb-lite-alpha-1.tar.gz
> $ cd eb-lite/
> $ ./configure --with-static-all && make
> <stuff>
> $ cd ebqt/
> $ ./configure && make
> <stuff>
> $ su
> Password:
> # cd ../
> # make install
> # cd ebqt/
> # make install
>
> Once the application is installed, you must first start the core (eb-lite),
> then the user interface (ebqt). If you want to try connecting a UI on one
> machine to a core on the other, enter the key (the sequence of numbers the
> core prints on stdout) and the host running the core into ebqt. If you're
> doing it on the same machine, this is done automatically.
>
> Installing and mucking around with EB-lite will not touch your current
> Everybuddy installation. I recommend for sanity's sake that you compile all
> the protocols in statically (./configure --with-static-all when compiling
> the core).
>
> Oh - and PLEASE send feedback!
>
> Meredydd
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.