Frank Heckenbach escribió:
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.
I have a problem here:
-#if defined(__linux__) -# include "bcclnx.h" +#if defined(__DJGPP__) +# include <dos.h> +# include <pc.h> #elif defined(__WIN32__) # include "bccw32.h" #else -# include <dos.h> -# include <pc.h> +# include "bcclnx.h" #endif
This break the Wattcom and TurboC targets, really they are unmaintained now, but I will prefer don't break it, if we can. So, what about other macros?, can we check for __unix__ or something similar?
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.
Ok, I put it in my to do list.
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
Ok, thanks.
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.
Ok, thanks.
M.Alvarez