NESICIDE V1.007

slobu · Post by **slobu** » Mon Aug 29, 2011 6:32 am

I'm in a position where I can easily load fresh installs of XP, Vista and 7. I'd like to provide useful installation testing info. Is there particular steps or order I should be installing things to get an example to compile? My own attempts so far have failed.

cpow · Post by **cpow** » Mon Aug 29, 2011 6:49 am

slobu wrote:I'm in a position where I can easily load fresh installs of XP, Vista and 7. I'd like to provide useful installation testing info. Is there particular steps or order I should be installing things to get an example to compile? My own attempts so far have failed.

Sorry, slobu, I completely missed your reply on the previous page.

slobu wrote:Tried to uninstall GNU Make, cc64 and NESICIDE and redo it with the updated files and still no compile. I'm fully willing to blame by Windows configuration for this. My next step is a fresh install of Windows followed by immediately installing your provided software.

If and when I get this working I'm thinking about using Installrite or Cameyo to make sure everything is correct and fool (read: me) proof Smile

UPDATE: Still getting no love on a fresh install of XP:
1. Install GNU Make
2. Install snapshot of cc65
3. Install NESICIDE
4. Open AlterEgo.nesproject in AlterEgo folder
5. Attempt to compile gives Build Failed message.

When you go to Help->About Nesicide in the application, and look at the "Versions" tab, what do you see for the versions of the CC65 tools and Make? If any of those are blank it's a problem with your PATH. I had an issue on a computer I tried installing NESICIDE on which turned out to be that the GNU Make installer hadn't added its info to my PATH, so NESICIDE couldn't find it. Same is true for cc65...you want to make sure to select the option to add it to your PATH.

I realize the output pane isn't very text copy/paste friendly at the moment, so could you paste a screenshot of the content of the output pane with the "Build Failed" message?

Feel free to PM me or email me...I can't get on IRC during work hours.

slobu · Post by **slobu** » Thu Sep 15, 2011 8:53 am

Sorry to take so long on this. Just got a fresh install of XP to test with. Same steps as before. Same results. Again, I blame end-user-itis on this. I did notice the "make" section was blank in the version tab. Is that the step that's missing? If so, given default install settings for each dependancy (GNU Make, cc65, NESICIDE) what is the next step? As a side I couldn't select all the text from the Output field. I had to copy-and-paste line by line (but, you knew that) :p

Contents of PATH statement:

Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cc65-snapshot\bin;;C:\Program Files\cc65-snapshot\bin

Version info:

NESICIDE Application version:
V1.007 RELEASE

NESICIDE Emulator Library version:
V1.003 RELEASE

Versions of external dependencies:
cc65:
cc65 V2.13.9
SVN version: unknown

ca65
ca65 V2.13.9 - (C) Copyright 1998-2011 Ullrich von Bassewitz
ca65.exe: No input files

ld65
ld65 V2.13.9 - (C) Copyright 1998-2009, Ullrich von Bassewitz
ld65.exe: Error: No object files to link

make

Output:

Project build started.
Building: obj/nes/alterego.prg
make all
Build failed.

cpow · Post by **cpow** » Thu Sep 15, 2011 9:18 am

slobu wrote:Contents of PATH statement:

Code: Select all

Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cc65-snapshot\bin;;C:\Program Files\cc65-snapshot\bin

Yes, GNU make did not put itself in your path during the install. I had the same issue on WinXP. I had to add:

Code: Select all

C:\Program Files (x86)\GnuWin32\bin

to my PATH.

EDIT: Fixed formatting.

slobu · Post by **slobu** » Thu Sep 15, 2011 9:38 am

Thanks for the fix! Actually, I just tried this on Win 7 32-bit and cc64 and make failed to put entries into the PATH.

I changed the environment variables -> PATH to:

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cc65-snapshot\bin;;C:\Program Files\cc65-snapshot\bin;C:\Program Files\GnuWin32\bin

Of course, end-users should avoid arbitrarily blowing away any existing PATH info. This is just to add cc65 and make locations in there.

Might I suggest checking for these PATH entries on install of NESICIDE and adding them if needed?

cpow wrote:
slobu wrote:Contents of PATH statement:
Code: Select all
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\cc65-snapshot\bin;;C:\Program Files\cc65-snapshot\bin
Yes, GNU make did not put itself in your path during the install. I had the same issue on WinXP. I had to add:
Code: Select all
C:\Program Files (x86)\GnuWin32\bin
to my PATH.

EDIT: Fixed formatting.

cpow · Post by **cpow** » Thu Sep 15, 2011 10:03 am

slobu wrote:Thanks for the fix!

So it works now?

slobu wrote:Might I suggest checking for these PATH entries on install of NESICIDE and adding them if needed?

If I can figure out how to do this with AdvancedInstaller, I'll do it. But I'm concerned that even if I could figure it out, it would be wasting time because the end user can install both packages wherever they want. How to deduce where they installed them if they're not evident in the PATH already?

slobu · Post by **slobu** » Thu Sep 15, 2011 11:53 am

Oops! Sorry, yes. It compiles. I might not understand how the debug emulator works as it results in a green screen. FCEU does run the ROM correctly though. Unless I'm picking out a pre-compiled .NES in the example project.

I would suggest checking out the PATH string for any cc65 or make entries. If none are found give a dialog that allows the end user to select a path or cancel to refrain.

I really believe your IDE could draw first time NES/C developers. It's visual enough and feature encompassing enough IMHO. Understanding the need for special entries in their path for make and cc65 may not be common knowledge.

cpow wrote:
slobu wrote:Thanks for the fix!
So it works now?

slobu wrote:Might I suggest checking for these PATH entries on install of NESICIDE and adding them if needed?
If I can figure out how to do this with AdvancedInstaller, I'll do it. But I'm concerned that even if I could figure it out, it would be wasting time because the end user can install both packages wherever they want. How to deduce where they installed them if they're not evident in the PATH already?

cpow · Post by **cpow** » Thu Sep 15, 2011 12:46 pm

slobu wrote: Oops! Sorry, yes. It compiles. I might not understand how the debug emulator works as it results in a green screen.

Any chance you can share the project content and project file so I can help you figure this out?

EDIT: I just thought...did you click the icon in the toolbar next to the "Compile" icon? That toolbar button loads the compiled ROM into the emulator. If you don't do this, when you hit the "Run" button you'll be running a blank ROM and get a green screen as a result. Yes, I know, a users guide would be very helpful!

slobu wrote: I would suggest checking out the PATH string for any cc65 or make entries. If none are found give a dialog that allows the end user to select a path or cancel to refrain.

Yes, I will do something like this.

slobu wrote: I really believe your IDE could draw first time NES/C developers. It's visual enough and feature encompassing enough IMHO. Understanding the need for special entries in their path for make and cc65 may not be common knowledge.

Thanks for the feedback. I'm presently almost ready to release a new version with a Tile Editor that should hopefully be very useful also.