I recently got given an Intel Mac at work, and when a problem arose I thought I could easily solve with Blitz I decided to give the demo another try. (Although I hate coding on Macs!).
I eagerly downloaded XTools 2.3 and installed it all, and fixed drive permissions (in single user mode with fsck), then I wrote a few simple lines and test compiled.
With the program
print "Hello World"
I get the runtime error
Compile Error
no such 386 instruction: `mlfr'
The editor opens up the document "untitled1.bmx.console.debug.macos.s" which looks like a load of assembly code, and the output window has reams and reams of errors like,
which goes on for pages and pages. So not to be outdone I wrote a little itsy witsy application on a PowerPC Mac and compiled it, but when I ran it on the Intel iMac I got this output from the Terminal window,
Yet the Intel Mac runs an application I wrote ages ago on the first demo version absolutely fine, I notice that when doing an apple-i to get file info my old application is described as:
Kind: Application (PowerPC)
but the new one (compiled on a PowerPC Mac) is described as:
Kind: Unix Executeable File (PowerPC)
Is this because it is in debug mode? To be honest, does debug mode work on an Intel iMac?
I see Intel Mac users are working with BMax fine and some clever sods have worked out how to make Universal binaries which is great - but I need to know the thing will solve the problem before I ask my boss to fork out £99.
PS: I pressume that when compiling on the full version the terminal window wont open?
I eagerly downloaded XTools 2.3 and installed it all, and fixed drive permissions (in single user mode with fsck), then I wrote a few simple lines and test compiled.
With the program
print "Hello World"
I get the runtime error
Compile Error
no such 386 instruction: `mlfr'
The editor opens up the document "untitled1.bmx.console.debug.macos.s" which looks like a load of assembly code, and the output window has reams and reams of errors like,
/Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:158:no such 386 instruction: `mflr' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:159:no such 386 instruction: `stmw' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:160:no such 386 instruction: `stw' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:161:no such 386 instruction: `stwu' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:162:no such 386 instruction: `lis' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:163:no such 386 instruction: `ori' /Applications/BlitzMaxDemo/tmp/.bmx/untitled1.bmx.console.debug.macos.s:164:no such 386 instruction: `lwz'
which goes on for pages and pages. So not to be outdone I wrote a little itsy witsy application on a PowerPC Mac and compiled it, but when I ran it on the Intel iMac I got this output from the Terminal window,
2006-07-11 13:28:19.457 AddressSync[359] CFLog (21): dyld returns 2 when trying to load /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn 2006-07-11 13:28:19.463 AddressSync[359] CFLog (21): dyld returns 2 when trying to load /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn Bus error logout [Process completed]
Yet the Intel Mac runs an application I wrote ages ago on the first demo version absolutely fine, I notice that when doing an apple-i to get file info my old application is described as:
Kind: Application (PowerPC)
but the new one (compiled on a PowerPC Mac) is described as:
Kind: Unix Executeable File (PowerPC)
Is this because it is in debug mode? To be honest, does debug mode work on an Intel iMac?
I see Intel Mac users are working with BMax fine and some clever sods have worked out how to make Universal binaries which is great - but I need to know the thing will solve the problem before I ask my boss to fork out £99.
PS: I pressume that when compiling on the full version the terminal window wont open?