Rockbox Development > Starting Development and Compiling
Weird compile error...help?
major_works:
I am compiling my own build for the e200. I have downloaded fresh SVN, but am adding a number of patches.
What happens is the following:
CC target/arm/sandisk/sansa-e200/adc-e200.c
CC target/arm/sandisk/sansa-e200/backlight-e200.c
CC target/arm/usb-pp.c
CC target/arm/sandisk/sansa-e200/button-e200.c
CC target/arm/sandisk/sansa-e200/power-e200.c
CC target/arm/i2s-pp.c
CC target/arm/sandisk/sansa-e200/audio-e200.c
CONVBDF
CC sysfont.c
Header parsed
AR+RANLIB librockbox.a
GENLANG
CC lang.c
CC action.c
CC alarm_menu.c
CC abrepeat.c
CC bookmark.c
In file included from bookmark.c:37:
recorder/icons.h:30:25: error: rockboxlogo.h: No such file or directory
make[1]: *** [/cygdrive/c/cygwin/bin/rockbox/build/apps/bookmark.o] Error 1
make: *** [build] Error 2
In looking closely at the above and comparing it to the log for the current Sansa build, I determined that the "No such file" error is due to the fact that the compile run is skipping over (not compiling) a whole bunch of stuff at this point:
AR+RANLIB librockbox.a
GENLANG (in here is where a lot of other stuff ought to be, including the rockboxlogo.h file that the compilation of bookmark.c can't find)
CC lang.c
I've been compiling my own patched builds for some time but have never seen anything like this before. I know it has something to do with the patches, because compilation of a clean SVN source tree works. I've had builds fail but not this way. Does anyone have any clue as to what's going on here?
digerati1338:
Sometimes something like this happens to me, either because of a bad patch or corrupted source/whatever.
Try
--- Code: ---svn revert -R ./
--- End code ---
That will remove all of your patches and give you clean svn code. If that doesn't work, I would just delete the source directory and check out SVN again.
major_works:
Thanks, Digerati. I did go with fresh SVN and finally was able to complete a build, this time without some of the patches I'd been trying to add. What I'm not quite sure about is which one(s) were causing the problem.
I reverted to a much simpler build with "essentials" (album art, .bmp resizing, and scroll margins) and that's what worked OK. I'd tried adding some of the ones being used in the pre-compiled builds on the ABI forums and that's when things went wrong. I'll have to experiment with them to see if I can determine which one(s) are the culprit(s).
bascule:
*Sometimes* they have to be applied in a certain order, as one builds on another. It's normally explained in the Flyspray entry, though.
major_works:
Thanks, Bascule... I'll look at the patches I removed for dependencies. Good suggestion.
Navigation
[0] Message Index
[#] Next page
Go to full version