Compiler Update - v2.3.14

Post by **dkinzer** » 21 February 2008, 13:49 PM

I've posted an update to the compiler that corrects the new problems that were discovered in the version posted yesterday. The .zip file contains an updated zxlib.h and a new file both of which go in the zxlib sudirectory of the installation directory. The .zip file contains the correct path prefix for both of those files.

http://www.zbasic.net/download/ZBasic/2 ... 2-3-14.zip

Don_Kirby · Post by **Don_Kirby** » 21 February 2008, 14:30 PM

It seems there's a path issue here.

>"C:\Program Files\ZBasic\zbasic.exe" --target-device=ZX24n --directory="D:\uG\ZBasic/" --project="ZXOnly.pjt"
make: Entering directory `D:/uG/ZBasic/Temp/ZXOnly'
[...]
avr-gcc -o ZXOnly.i1 -mmcu=atmega644p -L"C:/Program Files/ZBasic/zxlib" -Wl,-T,C:/Program Files/ZBasic/zxlib/zx_avr5.lds -u rtc_ISR -u int1_ISR MainTask.o RunSetup.o AlarmTask.o DisplayTask.o DimmerTask.o HourTask.o SensorTask.o LoadDefualts.o Globals.o ChangeLog.o ModbusTask.o -lzx24n -lm
avr-gcc.exe: Files/ZBasic/zxlib/zx_avr5.lds: No such file or directory
make: *** [ZXOnly.i1] Error 1
make: Leaving directory `D:/uG/ZBasic/Temp/ZXOnly'
Internal Error: an error occurred while building ZXOnly.zxc
>Exit code: 1

-Don

Post by **dkinzer** » 21 February 2008, 15:06 PM

Don_Kirby wrote:It seems there's a path issue here.

Indeed. Who's the genius that decided that allowing spaces in filenames would be a good idea?

I've updated the archive with a new zbasic.exe that quotes the filename. The version number remains the same.

Don_Kirby · Post by **Don_Kirby** » 21 February 2008, 15:45 PM

I've updated the archive with a new zbasic.exe that quotes the filename.

2 releases in 1 hour and 15 minutes... That has to be a record somewhere.

-Don

Post by **dkinzer** » 21 February 2008, 16:06 PM

Don_Kirby wrote:2 releases in 1 hour and 15 minutes.

The change required to correct the problem was extremely localized, only affecting one part of the makefile that is generated to perform the backend build. Consequently, we felt comfortable not running the entire testsuite prior to posting the new version for use by a limited audience.

I assume that you no longer see the problem.

Don_Kirby · Post by **Don_Kirby** » 21 February 2008, 16:31 PM

dkinzer wrote:I assume that you no longer see the problem.

That would be an accurate assumption.

No errors. Target device: ZX24n, Code: 34820 bytes, RAM: 1056 bytes, Persistent memory: 964 bytes
>Exit code: 0

dkinzer wrote:we felt comfortable not running the entire testsuite

I certainly didn't mean to imply that you should have, only that I'm having a hard time breaking the new versions as fast as you're releasing them. Can you at least make it appear like it's difficult? I don't know, make up big long descriptions of how difficult this or that problem was to track down. Whine a bit about the schedule slipping because of the bugs that crept in during that last revision. Blame the newest bug on the marketing team for promising features that weren't implemented yet. Perhaps make some vague remarks that you never get to see the kids anymore because they've got you locked in your cubicle till all hours of the night.

-Don