abush wrote:Chris, You mentioned that there are some licence issues, can you elaborate/paste some links?
I'm not a licence specialist, but since Celestia is GPL, I don't think you can legaly link it against a proprietary library. And you would need to do that to get hardware accelerated OpenGL. That being said I don't think any of the Celestia developers will take you to court for trying this.
abush wrote:And, what kind of work needs to be done in order to get Celestia to compile under CC? Is there a way to check if all the other "freeware" apps where compiled with CC too?
Since Celestia compiles both with VC++ and various versions of GCC, there is a good chance that only minor modifications are needed to get it to compile with CC.
Getting the GTK/Gnome version is probably feasible since these are C libraries. The KDE version is another matter, you would have to recompile all of QT/KDE with CC.
abush wrote:How DOES one attempt to compile Celestia with CC? Is it just a matter of changing the Makefile portion:
Don't tweak the makefile by hand, check the ./configure --help output:
Code: Select all
Usage: ./configure [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
[...]
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
CPPFLAGS C/C++ preprocessor flags, e.g. -I<include dir> if you have
headers in a nonstandard directory <include dir>
CXX C++ compiler command
CXXFLAGS C++ compiler flags
CPP C preprocessor
CXXCPP C++ preprocessor
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.