CVS build instructions?

[logan_number5]

I love this program, but sorry this is such a lame question..

I just downloaded the latest cvs snapshot and cannot
get started..

I assume one must use Makefile.cvs to get configure, etc...
but I can't even get that far:

[logan@envision celestia.cvs]$ make all
make: *** No rule to make target `all'. Stop.
[logan@envision celestia.cvs]$ make -f Makefile.cvs all
This Makefile is only for the CVS repository
This will be deleted before making the distribution

*** Creating acinclude.m4
*** Creating aclocal.m4
*** Creating configure
configure.in:25: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.in:396: warning: do not use m4_regexp: use regexp or m4_bregexp
*** Creating config.h template
*** Creating Makefile templates
src/celestia/kde/Makefile.am:12: invalid unused variable name: `KDE_SOURCES'
make[1]: *** [cvs] Error 1
make: *** [all] Error 2


I've searched scattered docs and these forums with no luck.

ml

[steffens]

You need to run autotools to generate your configure script. The sequence should be:

Code: Select all

aclocal
autoheader
automake
autoconf


If all goes well, you will have the configure script now.

[t00fri]

I love this program, but sorry this is such a lame question..

I just downloaded the latest cvs snapshot and cannot
get started..

I assume one must use Makefile.cvs to get configure, etc...
but I can't even get that far:

[logan@envision celestia.cvs]$ make all
make: *** No rule to make target `all'. Stop.
[logan@envision celestia.cvs]$ make -f Makefile.cvs all
This Makefile is only for the CVS repository
This will be deleted before making the distribution

*** Creating acinclude.m4
*** Creating aclocal.m4
*** Creating configure
configure.in:25: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.in:396: warning: do not use m4_regexp: use regexp or m4_bregexp
*** Creating config.h template
*** Creating Makefile templates
src/celestia/kde/Makefile.am:12: invalid unused variable name: `KDE_SOURCES'
make[1]: *** [cvs] Error 1
make: *** [all] Error 2


I've searched scattered docs and these forums with no luck.

ml

You need first of all a correct installation of KDE 3.x /including/ the header files from quite a few packages. These are often called
<name>-devel.rpm, if <name> stands for a given package (e.g. library name). Moreover further standard libraries and headers need to be installed.

Since you did not tell us /anything/ about your system (why??), no more concrete info is possible from here.

You also need a reasonably modern set of autotools! (autoconf, automake,...)

The 'make' statement, of course, can only work /after/ the Makefiles have been generated by means of the autotools, as usual. So why again did you type 'make all' at the beginning?

Was Celestia your first Linux compilation attempt?

In principle the appropriate configuration and Makefile generation takes place with the simple commands:

make -f Makefile.cvs
./configure

When this works without errors, you proceed by typing

make

and later, after a successful build,

make install.


Bye Fridger

[Christophe]

[logan@envision celestia.cvs]$ make -f Makefile.cvs all
This Makefile is only for the CVS repository
This will be deleted before making the distribution

*** Creating acinclude.m4
*** Creating aclocal.m4
*** Creating configure
configure.in:25: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.in:396: warning: do not use m4_regexp: use regexp or m4_bregexp
*** Creating config.h template
*** Creating Makefile templates
src/celestia/kde/Makefile.am:12: invalid unused variable name: `KDE_SOURCES'
make[1]: *** [cvs] Error 1
make: *** [all] Error 2

That's probably related to the version of the autotools you're using. Please report the version numbers.

A quick fix for you would be to replace KDE_SOURCES by its value in src/celestia/kde/Makefile.am. It's defined and used only in that file.

Another option is to use the latest snapshot from http://celestia.teyssier.org/download/daily which includes the configure script.

[Guest]

That's probably related to the version of the autotools you're using. Please report the version numbers.

A quick fix for you would be to replace KDE_SOURCES by its value in src/celestia/kde/Makefile.am. It's defined and used only in that file.

Another option is to use the latest snapshot from http://celestia.teyssier.org/download/daily which includes the configure script.

I'm using a stock RH9 install. I don't know which packages they are all in, but
autoconf-2.57-3
automake14-1.4p6-5.1
automake15-1.5-6
automake-1.6.3-5


I think the "daily" option is best for me. Thanks.
<FYI I nevertheless included further replies below>

You need to run autotools to generate your configure script. The sequence should be:

Interesting that this worked. I thought "make -f Makefile.cvs" would do it
since it seems to use admin/cvs.sh, which then seems to use these autotools.
At least the build made it all the way to the kde/ subdirectory.

In file included from eclipsefinderdlg.cpp:10:
eclipsefinderdlg.h:3:38: eclipsefinderdlgbase.uic.h: No such file or directory

But maybe I'll next build using: configure --with-kde
I'll try more forum searches from here..

Since you did not tell us /anything/ about your system (why??), no more concrete info is possible from here.

I wasn't asking about my system, I was asking about the "process" of building
celestia from a cvs checkout.

You also need a reasonably modern set of autotools! (autoconf, automake,...)

This is the first project I've seen where I need to use autotools -
guess I'm kind of naive, afterall. They seem to be quite useful
based on some quick www searches. Mostly projects still seem to
put "configure" in CVS.
I would have thought RH9 was somewhat up-to-date on the tools.

So why again did you type 'make all' at the beginning?

There is no "again" - this is the first time you asked.
It was a typo (I forgot to use -f Makefile.cvs), then it was a cut/paste error
to include it in the posting.

Was Celestia your first Linux compilation attempt?

I'll let that one go...

In principle the appropriate configuration and Makefile generation takes place with the simple commands:

make -f Makefile.cvs
./configure

THIS is the answer I was looking for. Since my assumption was correct,
and the commands from "steffens" works - that tells me cvs.sh may have
a minor bug somewhere. Or some other admin/ script.


thanks to Christophe and steffens for the help.

Mike

[t00fri]

Since you did not tell us /anything/ about your system (why??), no more concrete info is possible from here.

I wasn't asking about my system, I was asking about the "process" of building celestia from a cvs checkout.

But your system setup is most strongly correlated with problems you might encounter when trying to compile from CVS. Since we have no a priori idea about your skills in this matter, systems info is indeed crucial if you want help.

It costs our time if we have to guess around instead of judging on the basis of hard facts...

You also need a reasonably modern set of autotools! (autoconf, automake,...)

This is the first project I've seen where I need to use autotools - guess I'm kind of naive, afterall. They seem to be quite useful based on some quick www searches. Mostly projects still seem to put "configure" in CVS.

Open source development is globally based on autotools and there is never a configure script at the level of the CVS. Of course every official distribution of Celestia includes a configure script, too. But this is user level not CVS-developer level!

So why again did you type 'make all' at the beginning?

There is no "again" - this is the first time you asked.

It was a typo (I forgot to use -f Makefile.cvs), then it was a cut/paste error to include it in the posting.

The 'again' is a "Germanism". English is not my mother tongue. If you are disturbed by my occasional errors, I am always ready to continue in German. I can assure you that I will be more correct and you presumably less so;-)...

We definitely could not know that your 'make all' at the start of your error dump was a "typo", and I had to judge on the basis of what I could actually read from you...

Bye Fridger