Celestia Forums

Thanks, I finally understand it. Don't know why I was so dense about it before. Anyway, I really appreciate your help with this and thanks again.

Fridger, Thanks for your continued patience and help, but I must be missing something. I thought that the whole purpose of the excerise was to be able to run celestia from its build directory. What you are suggesting seems to require me to do a "make install", presumably as root. I was hoping that I...

Thanks again Fridger. With your help I got the rsync working. Now my problem is finding the right combination of ./configure parameters in compiling that will celestia to run from its build directory. As stated above, I would normally compile for a "real install" using the following: ./configure --w...

Fridger, I got it to work, well sort of. I changed your script as I am only interested in compiling for one desktop (KDE). Here is my modified script: celestia: rsync -avur --exclude ??*~?? --exclude ??*.dsw?? ~/CVS/celestia/ ~/Software/celestia-cvs all: celestia (Note: rsync line starts with TAB ch...

Thanks Fridger, I understand most of what you are saying but I am still somewhat new to linux. Could you please explain to a linux newbie how you sync-copy differences between the CVS and build directories using "rsync" in a Makefile? It sounds like you have built a special Makefile, or at least edi...

I have successfully compiled celestia CVS on my SuSE 9.3 linux box running the KDE 3.4 desktop. I asked a somewhat similar question months ago and got no response so I'll try again: After I compile the CVS is there any way I can get it to run from its build directory rather than having to install it...

I have successfully compiled the CVS version of Celestia on my SuSE 9.1 Pro linux system. I have a couple of questions, however. 1) Is the proper way to include lua to use --with-lua-inc=DIR OR --with-lua-includes=DIR (or is it --with-lua-include=DIR, without the "s" on include)? I know that the con...