-- Original message from "Anton Ertl" <[email protected]>: -------------- > You get one image when building (which contains your build path). > Upon "make install" a new image is generated that contains the install > path. So if you see the above before "make install", that's normal.
What was confusing me is that gforth.fi is removed in make install. Therefore, the behavior of ./gforth changed from what I saw after a make. The relevent lines from the install: /usr/bin/install -c -m 644 gforth.fi /usr/local/lib/gforth/0.7.0-20081226 rm gforth.fi install.TAGS Since soft links appear to be problemetic in cygwin, there doesn't appear to be a no good way to point to the new install. I'm still trying to figure out what works and I'll let you know when I figure it out. The problem is too many environments: Command Prompt uses C:\Program Files\gforth\gforth.EXE which needs a gforth.fi in /usr/local/lib/gforth/0.7.0 that matches it. cygwin uses /usr/local/bin/gforth as a soft link using the latest install. A batch file in cygwin must call the Program Files version. A script file in cygwin with the following in its first line: #! /usr/bin/env gforth ../../vf/gforth.fs gives: No such file or directory Loading ../../vf/gforth.fs on the next line of the script works, but defeats the ability to load it with VentureForth's executable. I guess I have to make that gforth conditional: S" gforth" ENVIRONMENT? [IF] 2drop include ../../vf/gforth.fs [THEN] It's not going to scale well, but for the moment, it's sufficient. ;( Is there a "better" way? DaR --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
