There is also no pleasing everyone as one way or another people will have to change paths to accommodate for their environment. If you use relative paths, and then move example application to a different folder, the parental structure will change and path won't work. If you set for home folder, and move application to somewhere else, the path won't work.
When I download some SDK/etc., I'm waiting that it will work and compile out of the box, and Asphyre is not. That is why I wrote about relative paths, because it will work at least for standard demos after unpacking the archive(but maybe this is your plan - make a bit higher barrier to entry for developers, and "cut off" too lazy people ). What about using the home directory - it will also work until Asphyre source code will be "installed" into it(I know two types of SDK - just an archive, and something installable ), but this is not an option for standard demos without description somewhere.