Frank Heckenbach escribió:
Then, I tried to build GRX on Sparc/Solaris. Besides having to set -lsocket as noted, there were a few more problems:
- Building shared libs failed. This might be a local installation problem since I've had some problems with shared libs there before, but it might also be a matter of compiler/linker options (ISTR that the options required very from system to system, that's why libtool was invented, but I don't know much about libtool myself). For now, I just disabled shared libs by editing the makefiles, but I think this should be possible via makedefs settings (or is it possible, how?).
Not at this time, note that makefiles are valid/tested only for the four supported platforms. For the (few) people interested in compile GRX in other platforms the changes they must to do to makefiles are easy.
- test/bgi/bccbgi.c fails because it tries to include <pc.h> (on every platform except Linux and mingw, while it only exists on Dos, AFAIK).
- same bug in test/bgi/fontplay.c
- same bug in test/bgi/tellipse.c
- same bug in test/bgi/tfill.c
- same bug in test/bgi/tpoly.c
- same bug in test/bgi/ttext.c
(diff12)
Thanks
- The install target(s) should created the directories (e.g. include, lib, info) before trying to write into them. This is particularly necessary when installing in a temp dir in order to build a binary distribution. (I didn't make a patch for that yet.)
I'm not sure if we must do it.
- /etc/infodir seems to be hard-coded in the makefile. That's bad! (Not everyone is root. ;-) I strongly suggest this directory to be configurable, and to make the whole install-info stuff optional
Ok, but people who use the install target are suposed to be root anyway.
(or get rid of it at all -- something like @dircategory and @direntry in the texi file might be better, since it allows the system tools which (re)build the info directory to recognize it).
Sorry, I don't know well TexInfo to understand this.
After working around these problems, however, I was able to build it and run the test programs and some of my Pascal programs successfully.
Great!
Another idea: How about a configure script for GRX? It could just make a copy or link of the respective makefile.foo to Makefile and set some options in makedefs from the command line. This way, it would be purely optional (i.e., the current way of building GRX would still work, but those who prefer ./configure && make (like me) could do that then).
If you don't reject the idea, I could probably write such a little script (only for X11, svgalib and perhaps DJGPP -- but I guess users on other platforms wouldn't expect to run configure, anyway (or mingw, maybe?).
I don't like it. Stock DJGPP an Mingw users don't install "sh" and I like the simplicity of makefiles instead of configure scripts.
Greetings, M.Alvarez