Note: the news posts might be rather
technical. Not interested in that? Just
pick the appropriate build directory from the right-side
menu and look at the last modified date.
If you’re on Windows and don’t know if you have a 64- or
32-bit system, go for Windows (32-bit).
Installer builds end in
‘-msi.zip’ .
debugger
Debugger builds
2010 Apr 02 @13:58
As the Mac users might have noticed, I’ve been
building Debugger builds on a daily basis, at the
same time as the regular openMSX builds.
Since the openMSX and openMSX Debugger projects both share the same repository, and since the builder script was only looking at the most recent revision number, a new Debugger was built every night and tagged with the latest revision number, even though nothing might have changed in the openMSX Debugger project.
I’ve updated the script a bit now so it should only build and release a new openMSX Debugger if there has actually been a change committed to the openMSX Debugger project. Besides this, I’ve also changed the directory to which the Debugger builds are published.
This means that the latest available Debugger build is revision 11151 and is available from the new Mac Debugger Builds directory.
The menu on the right has been updated accordingly.
Please note though that to make the About box show the correct revision number, I’ve applied a building hack by setting the CHANGELOG_REVISION variable myself. I do this because openMSX Debugger normally still determines its revision number from its Changelog, which hasn’t been updated since 10055.
This is a bug in openMSX Debugger and has been reported.
I’ve also updated some older news posts to hopefully reduce some of the technical terms for the Windows users. I kind of hope the Mac users to be more used to terms like x86 and PPC.
Since the openMSX and openMSX Debugger projects both share the same repository, and since the builder script was only looking at the most recent revision number, a new Debugger was built every night and tagged with the latest revision number, even though nothing might have changed in the openMSX Debugger project.
I’ve updated the script a bit now so it should only build and release a new openMSX Debugger if there has actually been a change committed to the openMSX Debugger project. Besides this, I’ve also changed the directory to which the Debugger builds are published.
This means that the latest available Debugger build is revision 11151 and is available from the new Mac Debugger Builds directory.
The menu on the right has been updated accordingly.
Please note though that to make the About box show the correct revision number, I’ve applied a building hack by setting the CHANGELOG_REVISION variable myself. I do this because openMSX Debugger normally still determines its revision number from its Changelog, which hasn’t been updated since 10055.
This is a bug in openMSX Debugger and has been reported.
I’ve also updated some older news posts to hopefully reduce some of the technical terms for the Windows users. I kind of hope the Mac users to be more used to terms like x86 and PPC.
Comments