Print

[sigma7]

With tremendous thanks due to Alex, I'm making progress going through the build processes with very few hiccups so far, this is one of the few.

In the folder of the Lisa source files for LisaWrite "Lisa_Source/APPS/APLW/", there is an anomaly in the naming convention that trips up the build process with a "file not found" error.

The anomaly is 3 files with names starting with "APLW." (case insensitive) instead of the usual convention "APLW-" (which are converted to APLW/ upon upload to the Workshop)

To fix this so LisaWrite would build successfully, in the Workshop I went to the File Manager, Selected R for rename, for the original files entered "APLW.=" and for the destination files "APLW/=" (that's assuming the default prefix that points to the hard drive, and don't type the quotation marks)

This should rename
APLW.T1ALERT.TEXT
APLW.D1BOX.TEXT
APLW.T1MENUS.TEXT

to
APLW/T1ALERT.TEXT
APLW/T1BOX.TEXT
APLW/T1MENUS.TEXT

[sigma7]

I see now that this is not a unique hiccup.

After building some libraries I see there is further confusion (for me at least) in file naming when there is a period in some names, such as LIBFE/FLD.main.text

In an earlier version of Alex's build scripts, the names were used as provided in the source download and in the more recent scripts the python patch script changes the references in the sources to replace the period with a /, eg. LIBFE/FLD/main.text, and so the files need to be renamed to suit as well as the references to them.

This may be a 'me' problem, as I was able to use the python patch script, but failed to get the pyserial module installed, so uploaded the files in another way. The method I used only replaced '-' with '/' but I suppose the python uploader also changes some '.' to '/', maybe there are no issues if you can go that route.

YMMV

Hopefully Alex can describe the rule for fixing the filenames...

[AlexTheCat123]

The rule with file naming is that you should replace all '-' with '/' and also all '.' with '/', other than the '.' at the start of the .TEXT extension.

The Python transfer script will automatically handle this for you, so I think the problem just stems from using some other transfer method that doesn't automatically do the renaming.

What issues were you having with installing pyserial? You should just be able to create a virtual environment, do 'pip3 install pyserial', and have it install properly, but it would be great to be able to update the readme with some additional instructions if there's any confusion!

[sigma7]

The rule with file naming is that you should replace all '-' with '/' and also all '.' with '/', other than the '.' at the start of the .TEXT extension.

As far as I can see, changing '-' to '/' is required to make the filenames match the source code, so it is a straightforward 'fix'.

However, it looks like changing '.' to '/' requires changing both source code and filenames, so not a 'fix' so much as a change of convention/style... not a big issue, but if further source code appears then it may be an ongoing one.

Is it the case that some source code was using the filenames with the '.' intact, and other source code was using the filenames with '/' substituted for '.', so you had to choose one convention or the other to unify?

Ultimately, given the huge challenge (and accomplishment) of getting all this to work at all (thank you!), I'll be satisfied to hear 'that was the easiest way to get it working', but still wondering if the problem is more complex.

[AlexTheCat123]

Is it the case that some source code was using the filenames with the '.' intact, and other source code was using the filenames with '/' substituted for '.', so you had to choose one convention or the other to unify?

Yeah, that's exactly how it was. The LisaWrite stuff was clearly substituting the '.' for the '/', but the Field Editor code (LIBFE) and maybe one other thing that I'm forgetting decided to actually use the dots as part of the filename. So instead of coming up with a complicated set of file naming rules (replace all '.' with '/' except in the special cases of...), I just decided to standardize it and replace all the dots with slashes.