Bug the Builder
James Lampard (51) 120 posts |
I’ve opened a ticket for this, but as it’s such a simple thing to fix, in case any one else is having the same problem I’m going to include it here as well. I’ve been using the following ‘Build directory’ with Builder ADFS::HardDisc4.$.Develop.ToBeInstal.2007_05_22.do_build.RiscOS This worked fine until I quit & reloaded Builder. Then although it appeared correct on the Menu – selecting it produced the error Directory ‘ADFS::HardDisc4.$.Develop.ToBeInstal.2007_05_22.d.Env’ not found Looking at the resource file I suspect this is due to the 50 character limit. Indeed changing !Builder.res window ‘Build options’ string set ‘Build directories’ fixes the problem. This is odd as the String set in the ‘Register build directories’ window already has a length of 128. |
Steve Revill (20) 1361 posts |
Very odd. It must be an oversight. Years ago, you had to have builds at or very near the root of your hard drive because of filename length problems but thankfully these are just a fuzzy memory now. I think this bug just reflects the fact that we’re still a bit cautious about where we put our builds. I’ll fix !Builer as you’ve suggested. |
James Lampard (51) 120 posts |
The latest version of the BBE dated Fri Feb 22 still has this bug. (Although the datestamps of the files inside !Builder have changed) |