Mariano Alvarez Fernandez wrote:
I have uploaded a pre-release of GRX 2.4.4. Download it from:
Works well for me, except that my "diff12" (some wrong inclusions on non-PC systems in test programs) hasn't been applied yet.
- 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.
If you don't, then install will copy, say, grx.h to a file called include instead of a file grx.h in a (non-existing) directory include.
Ok, my doubts was about the convenience to expand the /usr/local tree without user permission.
I think we can safely do it. Most other packages I've seen do the same.
- /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.
IMHO a very unfortunate attitude, also known as "Linux arrogance". There are actually Unix systems where not every user is or can become root (like, e.g., me on our university's machines), and they might want to install things in their home directory (which works with GRX except for the hard-coded /etc in one place).
Ops! I wanted to mean, that the automatic install target is normally for the superuser, normal users can move by hand the four files to the location they want (and the readme file says what files to move).
And I don't agree here. ;-) If they specify a suitable prefix directory (where they have write permission), they should be able to install it automatically IMHO. Apart from that, /etc/info-dir is not even correct on every Linux system -- on mine (SuSE) it's /usr/info/dir.
And the console linux target don't work at all if you are not supersuser, because it uses svgalib.
I'm not really talking about this one, 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.
Something like the following:
@dircategory Libraries @direntry
- GRX: (grx). The GRX Graphics Library.
@end direntry
Ok, thanks, where we must leave the info file?,
The location of the info file is ok, I think ($(INSTALLDIR)/info).
what utility must the user run after?
As far as I understand it (and see it in other packages), simply:
install-info --info-dir=$(INSTALLDIR)/info $(INSTALLDIR)/info/grx.info
Another thing:
I've now made GPC to allow `gpc-main' in units, so this can be inserted (conditionally for mingw) into grx.pas and graph.pas. Of course, it will work only with the next GPC version (probably released today), but earlier versions will simply ignore it (no warning), so I don't think it needs to be surrounded with a version check. The (additional) passing of `gpc-main' from the GRX/mingw Makefile will also not hurt, so it can be left there for a while (until the new GPC version has spread). So, in the future, no GRX/GPC user should have to worry about `gpc-main' in their programs.
That's in diff13. It also contains some minor cleanups in the Pascal files.
Frank