Suggest readme.txt be more explicit about running 'pforth -i system.fth'

[MaxBarraclough]

I suggest the readme.txt file be more explicit about how to build the dictionary file (pforth -i system.fth), as it's currently not very 'discoverable' for newcomers. Personally I googled it and found my way to this site, which spells out the steps.

[jgerrish]

Hey. Thank you for this project. I was able to build it and work with pforth, great experience. I used cmake for the build, which is where I came across initial issues with the dictionary file build.

Updating the readme.txt is one approach here, modifying CMakeLists.txt to support building in a non-root directory may also work. I could submit a PR for that if you wanted.

Have a great weekend.

[philburk]

I improved the README in #124

@jgerrish wrote:

modifying CMakeLists.txt to support building in a non-root directory may also work. I could submit a PR for that if you wanted.

Yes, I would appreciate any help you can offer with CMAKE.

[mschwartz]

If I wanted to install pForth in /usr/local/bin, where is pForth going to find the dictionary file? Where is it going to write it? Perhaps env variables?

I think it might be useful to be able to run a turnkey forth application from any directory…. Like we have save-Forth built in, maybe some kind of installer word built-in, too?

is shebang supported? Something like this would work:

somefile.f (chmod 755):

#!/usr/local/bin/pforth -i path-to-application forth code here (ASCII)

Just thinking out loud here…

[philburk]

@mscwartz - I created a new Issue for your topic. 3146 This topic is about compiling the original Forth code. Your topic is about loading pre-compiled dictionary files.

[philburk]

I am closing this because the docs have been modified. If jgerrish wants to submit a modified CMake file then that would be most welcome.