sabrecheeky
Member
- Joined
- Nov 16, 2005
- Messages
- 115
I am brand new to the gp2x - a great little machine. One main reason for getting it was the tantalising comment on gbax.com - "not since the amiga has a system been so easy to develop for" - which is good for me as the Amiga was the last system I developed for. And I quite liked the idea of brushing off the old coding cobwebs.
I come from a time before tool chains and all that madness. You had an editor, and a compiler. You typed your code - you compiled your code (you watched your machine crash spectacularly) - job done.
Life has moved on... Surely nowadays it should be even easier... Ha! So here is my tale of woe...
I followed Guyfawkes excellent GP2X guide to set up a development environment on my XP machine. Not too shabby - everything working. Tried his 'sdltest' download - compiled it, transferred it, ran it - no problems. Piece of piss I thought, but what was this thing called a 'makefile'? I'm sure it's not important.
Wrote a little code and thought I'll try to 'make' it - oh the naivety! Apparently 'make' is a UNIX thing that needs a specific 'makefile'. I wouldn't know a UNIX thing if it punched me in the face. It's bad enough getting used to a new machine without having to learn about UNIX. I had a look at said 'makefile' - UNIX text file on notepad - never a good sight. Bugger that I thought.
What I needed was an Integrated Development Environment (I believe I had one of these on my ZX81) so I unzipped the SDK which had been sitting on my Harddrive for months (I've only had my GP2X a fortnight). Nice little environment, seems quite friendly - a nice little menu item which says 'compile' - lets give that a shot. Created a project with Guyfawkes sdltest - lets go...
"Couldn't reserve 3600336 bytes of space for cygwin's heap, Win32 error 487"
What? WTF is this? WTF is cygwin? Did I only have maybe 3600335 bytes? Oh well - back to google. So cygwin is a UNIX like environment. And why do I need this? After hunting round here I find the problem to be 'cygwin-mkdir.exe' which does what? It uses a UNIX environment to make a directory in windows. Now I've used windows before; I'm pretty sure there is a command to make a directory in windows msdos command line.
So I install 'cygwin'. No idea why. Try again. Same error. This topic http://www.gp32x.de/board/index.php?showtopic=29372 mentions making a msdos batch file to circumvent this problem. This succeeded in giving me a different error code. This is upsetting as I now know there are at least 487 different errors.
Anyway running 'cygwin-mkdir.exe' on command line gives the error "can't find cygintl-3.dll". I went to C:\cygwin\bin and found "cygintl-3.dll" right away. How do you tell a PC that it didn't look bloody hard enough?
So which option should I go for...
A. Can anyone tell me an easy way in windows to create generic makefiles which I can use with Guyfalkes set up without learning yet another bloody language? OR...
B. Can anyone tell me how to sort out this problem with DevC++ calling cygwin error (as an amateur I think I'd probably prefer this)? A search has shown quite a few people have had this problem, but I cant seem to find a solution. OR...
C. Can someone tell me just to give up, its too complicated, and go back to messing with my Amiga A1200?
Thank you in advance!
I come from a time before tool chains and all that madness. You had an editor, and a compiler. You typed your code - you compiled your code (you watched your machine crash spectacularly) - job done.
Life has moved on... Surely nowadays it should be even easier... Ha! So here is my tale of woe...
I followed Guyfawkes excellent GP2X guide to set up a development environment on my XP machine. Not too shabby - everything working. Tried his 'sdltest' download - compiled it, transferred it, ran it - no problems. Piece of piss I thought, but what was this thing called a 'makefile'? I'm sure it's not important.
Wrote a little code and thought I'll try to 'make' it - oh the naivety! Apparently 'make' is a UNIX thing that needs a specific 'makefile'. I wouldn't know a UNIX thing if it punched me in the face. It's bad enough getting used to a new machine without having to learn about UNIX. I had a look at said 'makefile' - UNIX text file on notepad - never a good sight. Bugger that I thought.
What I needed was an Integrated Development Environment (I believe I had one of these on my ZX81) so I unzipped the SDK which had been sitting on my Harddrive for months (I've only had my GP2X a fortnight). Nice little environment, seems quite friendly - a nice little menu item which says 'compile' - lets give that a shot. Created a project with Guyfawkes sdltest - lets go...
"Couldn't reserve 3600336 bytes of space for cygwin's heap, Win32 error 487"
What? WTF is this? WTF is cygwin? Did I only have maybe 3600335 bytes? Oh well - back to google. So cygwin is a UNIX like environment. And why do I need this? After hunting round here I find the problem to be 'cygwin-mkdir.exe' which does what? It uses a UNIX environment to make a directory in windows. Now I've used windows before; I'm pretty sure there is a command to make a directory in windows msdos command line.
So I install 'cygwin'. No idea why. Try again. Same error. This topic http://www.gp32x.de/board/index.php?showtopic=29372 mentions making a msdos batch file to circumvent this problem. This succeeded in giving me a different error code. This is upsetting as I now know there are at least 487 different errors.
Anyway running 'cygwin-mkdir.exe' on command line gives the error "can't find cygintl-3.dll". I went to C:\cygwin\bin and found "cygintl-3.dll" right away. How do you tell a PC that it didn't look bloody hard enough?
So which option should I go for...
A. Can anyone tell me an easy way in windows to create generic makefiles which I can use with Guyfalkes set up without learning yet another bloody language? OR...
B. Can anyone tell me how to sort out this problem with DevC++ calling cygwin error (as an amateur I think I'd probably prefer this)? A search has shown quite a few people have had this problem, but I cant seem to find a solution. OR...
C. Can someone tell me just to give up, its too complicated, and go back to messing with my Amiga A1200?
Thank you in advance!
Last edited by a moderator:
