Support and General Use > Plugins/Viewers
How do I edit the Gigabeat Flashwriter to accept my checksum? Is it safe?
GodEater:
When you get errors, and are looking for help with fixing them, it's really useful if you actually post the errors.
It's really hard to help otherwise.
saratoga:
--- Quote from: BdN3504 on July 15, 2009, 04:39:00 AM ---i tried compiling that patch, but i always get some file not found errors. I placed it in the root folder using "patch -p0 <". Do i have to place this patch somewhere else?
--- End quote ---
Which patch is this exactly? The gigabeat flash writer isn't distributed as a patch . . .
LambdaCalculus:
--- Quote from: saratoga on July 15, 2009, 09:15:09 AM ---Which patch is this exactly? The gigabeat flash writer isn't distributed as a patch . . .
--- End quote ---
The original poster was talking about FS#7505, and BdN3504 was referring to that.
BdN3504:
Ok so first give you my setup:
i am running the old vmware Debian GNU/Linux provided on the wiki, have installed the crosscompiler and was also able to enable the tool window which let's me copy and paste from windows directly to start up with the vm.
now the first thing i do, when i started it up i cd to rockbox and do a svn update. i now have updated to revision 21883. now i downloaded the gigabeat_flash.c file provided by tom ross to the rockbox folder.
now when i normally download a patch and compile it with the svn i simply do the patch command like i mentioned above. But what puzzles me with this plugin is that it's extension is c as in a normal programme, not a standard rockbox patch or diff file. so why should patch create something usable with such a file? maybe you could elaborate on that...
so i now try
patch -p0 < gigabeat_flash.c
and get this output:
patch: **** Only garbage was found in the patch input.
that's because of what i already mentioned i guess, ...flash.c being c and not patch or diff. So logically what i want to do now is simply compile that file using gcc right?
so now i try
gcc -o flasher gigabeat_flash.c
and get this output.
am i using gcc wrong? i thought the "-o flasher" option directs the output into the file flasher and gigabeat_flash.c is the input. did i miss something here?
hm putting that c file into apps/plugins and then compiling a normal build didn't create any errors for the first time, but there also is not a sign of an application in the folder where i "make"'d that build. how do i access it?
saratoga:
--- Quote from: BdN3504 on July 15, 2009, 02:45:01 PM ---now when i normally download a patch and compile it with the svn i simply do the patch command like i mentioned above. But what puzzles me with this plugin is that it's extension is c as in a normal programme, not a standard rockbox patch or diff file.
--- End quote ---
Yes as I said above the flash writer is not a patch, so you cannot use patch to install it. Instead you'll have to put it in your plugins folder, and add an entry to the SOURCES file in the plugins folder so that it is compiled.
--- Quote from: BdN3504 on July 15, 2009, 02:45:01 PM ---gcc -o flasher gigabeat_flash.c
and get this output.
am i using gcc wrong?
--- End quote ---
For future reference, you cannot compile programs for your mp3 player using the x86 linux compiler since the CPU and operating system are different. If you want to compile them with gcc outside of rockbox, the command would be arm-elf-gcc, but that still will not work in this case since plugins cannot be compiled alone since they link large parts of the rockbox code.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version