The case of Resource paks

[noway]

Right now it is a pain to get OS from compiling to working due to resource packages. They are already downloaded during the compilation times (at least they should be, might have broken down), but still they are not automatically hooked up until you make install.

As an option to solve this, maybe employ flat built files directory structure in ./openspades.mk/? A build directory, for example build/ or build/linux-x64/ would contain all compiled *.os, *.sos, *.as, executables, as well as *.pak files. That way it would be easy to just stat the pak files in the directory containing $0. And on make install there is no difference in what is the source directory of a file being installed.

Also the messages which pop up when there are no paks could be more informative, because missing CMUSansCondensed.png does not really say what's wrong. Would be really cool to have an error handler specifically for not found resources which would tell user that the user might have forgot to download the resource paks, that there are the resource paks which were loaded successfully (if any), that a certain amount (a number? a 0 or '>1' flag?) of files/scripts were loaded straight from file system and the directories OS is looking for when loading the resource paks.

The last one sounds like a burden to implement though.