Re: [cc65] NES Development - Playpower introduction

I don't know much about NES, but I like your project and I just wanted
to give my 2 cents.

I second the idea to use C, even just as a sort of "scripting
language" for routines written in Assembly. If I remember correcly, if
you avoid complex routines like sprintf, the space overhead should be
fine.

I don't quite get how developing an IDE would be cost effective,
though. In my opinion, a command line tool would do the trick just
fine. I'm thinking about a sort of front end to the cc65 toolchain
hiding Makefiles, tools and configuration files.

For example, after running "NESToolsSetup.exe", you would get
"makenes.exe" in your path. Then, typing:

  makenes game.nes main.c module1.c module2.c sprites.png chars.png

would allow you to include "sprites.h" and "chars.h" from your C files
and would produce a "game.nes" file ready to run.

Regards,
Emanuele

On Tue, Feb 17, 2009 at 9:37 PM, Derek Lomas <dereklomas@gmail.com> wrote:
> I'd love to jump in and say hello, as well.  I've been following this list
> for several months now, as I'm helping to coordinate the playpower.org
> project, which is using $12 famicom-clones as a platform for computer-aided
> learning games in developing countries.  One of our major goals is to make
> the famicom-clone more accessible to developers by creating an open-source
> IDE for the NES-6502.
>
> We've been successful at creating new ASM code, loading it onto cartridges
> (with EEPROMs), and playing it in our famiclones.  But ASM isn't terribly
> accessible.   nBASIC is another "language" we've looked at for producing new
> NES code...  but this has a pretty high failure rate, and we haven't been
> able to get the compiled code to work in actual cartridges.
>
> The cc65 C compiler could potentially be the perfect platform for NES
> content development--I was especially excited to see Tachdaun's contribution
> of the v0.1 NES library.  Currently, lawrence and a few other students are
> working on producing some sample code that will compile and function in an
> actual cartridge in an NES and our famiclone.  Is anyone aware of previous
> attempts to do this?
>
> I really appreciate all that you have accomplished with cc65.  I hope that
> the playpower.org community will eventually be able to meaningfully
> contribute to cc65 -- and in the meantime, thanks in advance for your
> help.   Suggestions and advice are always welcomed.
>
> Cheers,
> Derek
>
> www.playpower.org
> skype: cognitiveculture
> m: 917 544 4171
>
>
> On Tue, Feb 17, 2009 at 12:21 PM, Lawrence Leung <lcleung@ucsd.edu> wrote:
>>
>> Hi everyone,
>> I have been ghosting this list for a little while and I've noticed that
>> there have been conflicting reports on whether or not the atmos.lib file is
>> needed to compile certain .nes files. I know for that the simple "hello
>> world" needs the atmos.lib file to be compiled correctly but the sample
>> "controllertest" from the cc65 website does not. Could somebody clear up the
>> function of this library?
>> Thanks,
>> Lawrence
>
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.