#176103 - Ben_j - Mon Apr 11, 2011 3:43 pm
I can't use my homebrew without wifi, so it's kind of a pain in the ass for testing :
- Compiling...
- Take Supercard off...
- Take micro sd off...
- Plug Micro-SD on computer... Click on the various Windows 7 messages
- Copy nds file...
- Take Micro SD off, plug it back to the Supercard, plug the supercard on the DS
- Start 3DS (super slow)
- Start homebrew
- Wait for wifi to connect
- Realise you forgot ++i; in a loop
- Le Fu
- Going back to step one
So, all in all, it takes roughly 30 seconds each time I want to test the homebrew. I've got the wifi version of DeSmuME but couldn't get it to work with my homebrew.
#176104 - elhobbs - Mon Apr 11, 2011 5:05 pm
I always try to make my projects compile for the ds and for my host environment - windows. that way I can use the visual studio debugger - which is much much easier. I have not used the 2d hardware though - only 3d - which is easy to abstract for windows. 2d would be a little harder - but if you use one of the 2d apis like gl2d that uses the 3d hardware it would be easier.
#176105 - Ben_j - Mon Apr 11, 2011 5:32 pm
| elhobbs wrote: |
| I always try to make my projects compile for the ds and for my host environment - windows. that way I can use the visual studio debugger - which is much much easier. I have not used the 2d hardware though - only 3d - which is easy to abstract for windows. 2d would be a little harder - but if you use one of the 2d apis like gl2d that uses the 3d hardware it would be easier. |
Why are you talking about 2d and 3d ? I want wifi emulation
#176106 - elhobbs - Mon Apr 11, 2011 5:46 pm
I assumed you were using dswifi - which has a socket implementation which is portable - mostly. the main obstacle to compiling your code for windows would be the 2d hardware specific code - which you would need to abstract. if you could compile for windows then you could find all of the "++i;" business in a much easier environment.
now if your project is to rewrite the dswifi library, then you are out of luck.
EDIT: I also forgot to mention that wifi emulation in desmume does not work so well - work in progress I think.
#176107 - Ben_j - Mon Apr 11, 2011 5:54 pm
| elhobbs wrote: |
I assumed you were using dswifi - which has a socket implementation which is portable - mostly. the main obstacle to compiling your code for windows would be the 2d hardware specific code - which you would need to abstract. if you could compile for windows then you could find all of the "++i;" business in a much easier environment.
now if your project is to rewrite the dswifi library, then you are out of luck.
EDIT: I also forgot to mention that wifi emulation in desmume does not work so well - work in progress I think. |
you mean compiling the homebrew as a windows executable ?
#176108 - elhobbs - Mon Apr 11, 2011 5:59 pm
exactly, it take a little bit of effort though.
#176109 - Ben_j - Mon Apr 11, 2011 6:02 pm
I don't think it would be worth it...
Another solution for me would be DSerial emulation :)
#176110 - elhobbs - Mon Apr 11, 2011 6:10 pm
you could also try wintermute's dslink. it downloads and launches an nds file over wifi - not sure if that works on a 3ds though.
#176111 - Ben_j - Mon Apr 11, 2011 6:15 pm
| elhobbs wrote: |
| you could also try wintermute's dslink. it downloads and launches an nds file over wifi - not sure if that works on a 3ds though. |
does it have a link with the DSLink flashcart ?
#176112 - elhobbs - Mon Apr 11, 2011 6:25 pm
no - it is just an nds file - a wifi bootloader. it would save swapping cards though.
I always go back to swapping cards when I need to test on the ds. it is annoying, but it is the most straight forward for launching something on a ds. fat access is so slow in emulators. I can have the card updated and back in and running faster than the emulator.
debugging in windows is well worth the effort though.