headers
Lane Schwartz | 13 Feb 2005 20:02
Picon
Gravatar

More compilation problems & where to go from here... KDE, command line, static link

Hi guys,

I just installed Fedora Core 3 on my machine at home. And I'm having a
heck of a time getting Workrave to compile. I can't seem to find a
stable libgnomeuimm rpm, and without that, workrave won't compile.

I guess I'd just like to add my voice to the others who have asked for
an easier way to compile/install workrave. I love it, and it has been
a Godsend for me at work (Mandrake 10.0).

But some some of statically linked version, and/or low-dependency
command-line version would be greatly appreciated.

Another possible route would be a KDE version. I am somewhat
interested in pursuing this track. Rob, could you possible outline
what work would be required for a new frontend (either command-line w
simple pop-up window or a KDE frontend)?

Thanks,
Lane
--

-- 
Meetup with other Myth users!
http://mythtv.info/moin.cgi/MUG

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rob Caelers | 15 Feb 2005 13:24
Gravatar

Re: More compilation problems & where to go from here... KDE, command line, static link

Hello,

> I just installed Fedora Core 3 on my machine at home. And I'm having a
> heck of a time getting Workrave to compile. I can't seem to find a
> stable libgnomeuimm rpm, and without that, workrave won't compile.

It shouldn't be too difficult to remove the dependency of libgnomeuimm..I think.
Though you will loose session management and the native applet.

> But some some of statically linked version, and/or low-dependency
> command-line version would be greatly appreciated.

In the past, I've build statically linked versions of Workrave. Unfortunately, I had to
create them manually. If you know an easy autoconf-ed way to created a statically linked
version, I very interested.

> Another possible route would be a KDE version. I am somewhat
> interested in pursuing this track. Rob, could you possible outline
> what work would be required for a new frontend (either command-line w
> simple pop-up window or a KDE frontend)?

I'm currently reviving the text-only frontend. This frontend was originally written to
check the memory usage of the backend. It will be in no way a viable replacement for the
gtkmm GUI. However, It does show what is expected of a frontend. Basically, a frontend
must create the backend and implement one interface (AppInterface). This interface is
used by the backend to inform the GUI that it must present/hide a break or break warning
window. The frontend can use a number of interfaces to control the backend and to obtain
information from the backend (timer values, break settings, activity state of user etc).
All of these inferfaces can be found in backend/include.
(Continue reading)

Permalink | Reply | 0 comments |
headers
lists | 3 Mar 2005 08:46

(no subject)

Hello All,

I am trying to compile workrave on SUSE 9.3 (still in beta, but I dont
think thats the problem).

amunshi <at> linux:~/workrave-1.6.2> gcc --version
gcc (GCC) 3.3.5 20050117 (prerelease) (SUSE Linux)

amunshi <at> linux:~/workrave-1.6.2> rpm -qa | grep nauti
nautilus-2.9.91-3

./configure went well, I satisfied all the dependencies, and then started
with make. I get the following error. Any clues on whats wrong?

amunshi <at> linux:~/workrave-1.6.2> make
make  all-recursive
make[1]: Entering directory `/home/amunshi/workrave-1.6.2'
Making all in m4
make[2]: Entering directory `/home/amunshi/workrave-1.6.2/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/amunshi/workrave-1.6.2/m4'
Making all in po
make[2]: Entering directory `/home/amunshi/workrave-1.6.2/po'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/amunshi/workrave-1.6.2/po'
Making all in backend
make[2]: Entering directory `/home/amunshi/workrave-1.6.2/backend'
Making all in src
make[3]: Entering directory `/home/amunshi/workrave-1.6.2/backend/src'
Making all in unix
(Continue reading)

Permalink | Reply | 1 comment |

Gmane