> Hey,
> I wanted to have a peek at the latest version so I aquired the CVS version
> of kmatplot off sourceforge. I had to do a couple things just to get it to
> start compiling.
> 1) uncomment line 12 in Makefile.am which says:
> $(top_srcdir)/configure.in: configure.in.in $(top_srcdir)/subdirs
> as autoconf complained about it.
I even don't know what this line is needed for. Automake stuff is based on
templates from KDE project of KDevelop, I've only added a few tests to it. It
seems to be too complicated, but everything works here on my computer.
After checking out a module I invoke :
make -f Makefile.dist all
./configure
make
and it goes without problems.
> 2) I also had to remove pixmaps from line 4 in kmatplot/Makefile.am
> It appears that the kmatplot/pixmaps directory is not in CVS
> 3)Make complained that it couldn't make kmatplot/formula/mpsymbol.o so I
> copied copied mpsymbol.h & mpsymbol.cpp from the 0.31 distrbution. (They
> are required for mpsymbols.o as well)
> I'm now stuck as qsconsole.h & .cpp seem to be required and they are not in
> CVS. Would it be possible for you to refresh the sourceforge CVS against
> your working directory as several files appear to be missing?
I'll try to fix those errors in a few days. I recently made big changes. I
removed a few dozens of files and added dozens of other files and apparently
got out of sync. I think it's the time to start using some automated tool
for managing CVS instead of those shell commands ;)
> Is it worth me playing with the CVS version or are too many things changing
> to make it worth while?
Current CVS version uses Qt 3.0.1 and doesn't use KDE libraries. It is quite
usable, I only have to fix some smaller errors.
> I know some C++ and have done Qt programming in the past. If you would like
> some help I can do the odd small job or some documentation. I am quite
> busy, but would like to see this program improve.
Of course, any help would be greatly appreciated but I can't tell you what to
do, so if you have any ideas ... and there is never enough documentation (
especially because currently there is no documentation at all ).
Kamil
|
