Hacking Question Porting error...

  • Thread starter Thread starter GalaxyYT
  • Start date Start date
  • Views Views 1,944
  • Replies Replies 7

GalaxyYT

Well-Known Member
Member
Joined
Feb 27, 2017
Messages
112
Reaction score
152
Trophies
0
Age
37
XP
728
Country
Canada
So, I'm trying to port a retroarch core to the Switch like a lot of other people have been doing. I'm a pretty big noob at coding in general, but I've been looking at the lib transistor usage page, the fceumm switch target, etc. Below is the picture of the code I'm using to make the emulator (parallel-n64). There's obviously more, this is just the snippet of switch code:
DnjVXmM.png


After running make, this is the console output:
dWBoSbm.png

I'm assuming I need to create a "rule" (line(s) of code?) to make the paran64.o file I specified near the top? I just really want to figure out how to port this emulator, even if it doesn't run well/at all. just trying to get that .nro file.
Edit: Got rid of 2 lines of code, and it got rid of the top 2 errors:
Makefile:137: warning: overriding recipe for target 'clean'
Makefile:68: warning: ignoring old recipe for target 'clean'
 
Last edited by GalaxyYT,
I haven't looked at parallel-n64 specifically, but most of the time porting something isn't as easy as just trying to compile it for a different platform. It can take lots of work to port things.

I'm assuming I need to create a "rule" (line(s) of code?) to make the paran64.o file I specified near the top?
From GNU: "A rule appears in the makefile and says when and how to remake certain files, called the rule's targets (most often only one per rule). It lists the other files that are the prerequisites of the target, and the recipe to use to create or update the target."
 
  • Like
Reactions: The9thBit
I haven't looked at parallel-n64 specifically, but most of the time porting something isn't as easy as just trying to compile it for a different platform. It can take lots of work to port things.


From GNU: "A rule appears in the makefile and says when and how to remake certain files, called the rule's targets (most often only one per rule). It lists the other files that are the prerequisites of the target, and the recipe to use to create or update the target."
Thanks for the info. Found the full article to help me a bit. Also, the SNES9x2010 port was ported a day after the latest version of libtransistor was released, which supports 5.x, which means they ported it in a day. No one has released the modified sources yet, though :(
 
Wow, only a day? Does RetroArch make it easier to port emulators? I could totally be wrong since I haven't messed around with RetroArch much though. I thought it was only an interface to launch emulators.
 
Wow, only a day? Does RetroArch make it easier to port emulators? I could totally be wrong since I haven't messed around with RetroArch much though. I thought it was only an interface to launch emulators.
They're only porting one core, not the whole retroarch/libretro application.
 
They're only porting one core, not the whole retroarch/libretro application.
I just read this page, so once the main libretro API is ported it makes it easier to port cores to the platform?

I don't know enough about the Switch and RetroArch/libretro to be much help, sorry.
 
I just read this page, so once the main libretro API is ported it makes it easier to port cores to the platform?

I don't know enough about the Switch and RetroArch/libretro to be much help, sorry.
I'm guessing that's the case, yes. since the ported snes9x source files include the libretro files.
 
Wow, only a day? Does RetroArch make it easier to port emulators? I could totally be wrong since I haven't messed around with RetroArch much though. I thought it was only an interface to launch emulators.
Depending on how the emulator is originally programmed, you can sometimes port to a working beta stage in mere hours.
 

Site & Scene News

Popular threads in this forum