Okay, everybody, I'm thinking about changing the #includes to absolute file paths so that gcc can find the .h files. I believe that changing it to something like this:
Ok, I'm currently in the process of making all #includes in all PT files and dependencies absolute file paths instead of relative. Hopefully this will work...
Excimer-Sun-Software "Lol! Ubuntu was that difficult to make work?" no, linux in general. the hardware in my laptop is designed to only allow windows. i have to boot with commanline: acpi=off noapic pnpbios=off so no power controll, sleep mode, special keys(volume up down etc).
"Ok, I'm currently in the process of making all #includes in all PT files and dependencies absolute file paths instead of relative. Hopefully this will work..."
From what I've read, I believe gcc will follow absolute filepaths in #includes, I'm just not sure what the right syntax to include absolute paths is. I think it's '#include "filepath"' but there's a small chance that it's actually '#include <filepath>'. If anyone here knows, I would be very greatful for the information. In the meantime, I'm nearly finished with implementing option one.
I'm closer! It's now finding such files as stdio.h, stdarg.h, and others! I appear to have missed some #includes and there appear to be a couple of discrepencys that need fixed, but it's now finding the .h files via the absolute file paths!
i think that there should also be a PT for Zune HD just because i have one (and so do many others) and it would just be nice because though its not as good as the ipod (app wise) its still a nice little gadget to have, so... yeah. just throwin that out there