monkeyDemo on my Macbook cant choose HTML5
Community Forums/Monkey Talk/monkeyDemo on my Macbook cant choose HTML5
| ||
| I am trying to run the Hitoro basic game demo on my Macbook (specs in sig.) but when I try to run it it asks me for a target but the target options is blank and does not run. the monkey application folder is in the applications folder Last edited 2011 |
| ||
| It might be a problems with file permissions, like some people have had with the IDE: http://www.monkeycoder.co.nz/Community/posts.php?topic=49 |
| ||
| that didn't work. I don't get any errors with Mark's suggestion but with Simon's suggestion I get this error: trans_macos: Bad CPU type in executable that's for the intel core duo. Last edited 2011 |
| ||
| Eek, think I found the problem here, Mark monkey stdcpp target should possibly use following flag: g++ -mmacosx-version-min=10.4 test.cpp more info on stack overflow |
| ||
| Hi, Monkey needs Snow Leopard on Mac for development! Will fix store page ASAP. Last edited 2011 |
| ||
| Better update the store page on the monkey site then: Mac Requirements: Mac OS X 10.3.9 or higher; Xcode installed http://www.monkeycoder.co.nz/Store/_index_.php Can I ask why (M?)monkey needs MacOS 10.6 for development? Last edited 2011 |
| ||
| I also want to know why it needs osx 10.6 for development? .. Last edited 2011 |
| ||
| Hi, > Can I ask why (M?)monkey needs MacOS 10.6 for development? Mainly because XCode 3.2.5 needs it and I do not want to be maintaining multiple xcode targets. I can't justify the extra time/expense of supporting another host platform beyond XP, Vista/7 and the latest MacOS. With 7 (5 Mac?) targets, that's a LOT of validation to be done. If you want to develop for iBlah, get used to this - things move pretty fast and if you want to keep up with the latest 'gee wizz' stuff like retina displays and so on you'll need to be keeping both your copy of XCode and your OS up to date. In general, our philosophy with Monkey will be to keep up with new SDK releases as rapidly as possible so as developers you will also be required to keep up with things too to a degree. Last edited 2011 |
| ||
| Interesting Philosophy, I like. This is Non-sequitur to the Blitz products tradition. I just hope it falls true for updates to come. out of curiosity, will updates come in the $charge$ category? I guess I'll pay the $29 to upgrade my OSX. :( I am starting to wonder if the rest of the products namely BlitzMax will suffer from attention. Not that they are getting a lot but I fear a lot less. |
| ||
| out of curiosity, will updates come in the $charge$ category? Apple's major updates may cost you a bit. Monkey's purchase link says: "Plus: Free lifetime updates - no upgrade costs or subscriptions". |
| ||
| I have Mac OS 10.6, but still can't run anything in the demo because the HTML5 target doesn't display. |
| ||
| did you tried Mark's and Simon's suggestions? what processor is it running on? |
| ||
| Yes, I checked the file permissions on the folder and it was to read and write. I'm using an Intel Macbook with Snow Leopard. |
| ||
| I checked the file permissions on the folder and it was to read and write. This is not the same as the executable bit missing on the bin/trans_macos file. If you haven't already, try unzipping the demo version using the built in MacOS Archive Utility. |
| ||
| did you tried Simon's suggestion? I got an error telling me it was the wrong processor. what I mean by the processor is it the core2 duo or just the Core Duo? I am looking for a pattern here. Last edited 2011 |
| ||
| Jesse, the wrong processor message is definitely due to you not running MacOS 10.6 and nothing to do with the processor in your computer. |
| ||
| Ok thanks. I am still wondering why he is having the same problem I have if his OSX is the correct one. |
| ||
| Yes, I unpacked the zip file several times with the default archive utility and all is there including the bin/trans_macos file. Monk opens and I can access he sample files, but when I compile, it doesn't give any options and doesn't open anything when I run it. |
| ||
| From the console, can you change directory to the monkey/bin directory and type ./trans_macos if it complains about permissions then type chmod +x trans_macos and try it again... |
| ||
| I've tried the suggestions and the console comes up with the following error: Bad CPU type in executable |
| ||
| well I have been doing some search on google and this is what I found so far: Ok. Problem solved. I posted my question on the x-unix mailing list and Juan Manuel Palacios came up with the following: Aha! Here, this next line calls gcc with the "-fast" optimization flag. Well, it turns out that Apple's gcc default configuration causes this flag to produce binaries *exclusively" for the G5 architecture... how do you like that?? If you're not on a G5 when compiling gcc will not complain or bail out with an error, it'll just compile along producing a binary which can only be used on G5s. You can still use the flag on other than G5 Apple architectures, but to get usable binaries you need to add "-mcpu=7450", right after the "-fast" flag. You can try this yourself: write a simple, one liner, test.c C program and compile it with "gcc -fast test.c -o test", then use file(1) on it (you'll simply get "Mach-O executable ppc", thus revealing nothing) and try to execute it... see? now compile the same thing with "gcc -fast -mcpu=7450 test.c -o test" and try to execute it... what do you get? It looks like you have some autoconf script editing to do (lines trimmed for reasons of message size): /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -fast -Wall -Wno-unknown-pragmas -pedantic -c -o aca.lo `test -f 'aca.c' || echo './'`aca.c I don't know if this is any help but sounds like it's the solution. |
| ||
| Game Boy, can you please confirm exactly which version of MacOS and processor you are running (apple menu->about this mac). Last edited 2011 |
| ||
| Processor 1.83 Ghz Intel Core Duo with OS 10.6.6 Sorry to be a pain for you :-). |
| ||
| oh! |
| ||
| Oh? That doesn't sound good, lol. |
| ||
| Sorry one more question, which version of XCode do you have installed? |
| ||
| My X-Code is version 3.2.5. Last edited 2011 |
| ||
| mine is 3.0. I am thinking we are out of luck due to the processor as yours is the same one I have except mine is a few GHZ faster. |
| ||
| Maybe there is an issue with the latest version of X-Code? |
| ||
| I am going to pick up to pick up the version of osx 10.6.3. I'll be able to testify in about 3 hrs. |
| ||
| I'll check back tomorrow - thanks for your help. Aren't you worried that you wont be able to use monkey? |
| ||
| It looks like Core Duo are only 32 bit processors where as Core 2 Duo are 64 bit. Hopefully its a quick fix for monkey binaries to be compiled for both in future. |
| ||
| I shall look forward to the update... |
| ||
| yea me to. I did upgrade to 10.6.3 and yea; same error. I was going to buy monkey as soon as it came out but I am glad I waited. Now I am just wondering if I really needed to upgrade OSX as now I am sure Mark wasn't really sure about what he said. just to note: xcode 3.2.5 requires OSX 10.6.4. Last edited 2011 |
| ||
| There is a new demo available on monkeycoder for you guys to try. Good luck! |
| ||
| Yea boy! Thanks Skid. Works great. and as I figured it works with Xcode 3.0 and I guess the demo also works with OSX 10.5.8 but I won't know for sure now. |
| ||
| @Jesse - I've just done a test on our OSX 10.5.8 Mac Mini (2.26Ghz Intel Core 2 Duo)... And it works fine! Just compiled my MonkeyPong app using the demo (MonkeyDemo30) and it compiled then launch Firefox and my game appeared! I altered the code in Monk on the mac and re-compiled, my changes were visable - just in case it was just opening the build from windows. And our xcode is version 3.1.4. |
| ||
| Thanks Skidracer and Mark Sibley - it works great now. Looking forward to testing Monkey and integrating it with my web projects :-). |
| ||
| Thanks for the info therevills. I really didn't want to spend the ~$32 to upgrade the OSX, not yet anyway and I am kind of sad I had to spend it because now I am going to have to wait a little longer to buy the full version. Oh well, life goes on. I almost forgot again: Thanks Mark for the update. Last edited 2011 |
   |