Alow `.hpp` files (and others) for `particle compile`

[ScruffR]

Since I've come across similar questions like this one before, I'd like to propose an enhancment https://community.particle.io/t/error-when-using-makefile-eclipse-for-debugging/42913/3?u=scruffr

There are some contributed libraries that use .hpp files and they seem to be buildable once the files are uploaded correctly (e.g. via particle library upload) but can't be built with local copies of the library due to the refusal of CLI to upload anything but .ino, .h, .c & .cpp. But it is common practice to have "template implementation headers" seperated from .h in .hpp files (or some other non-standard extensions).

So if we could also provide a way to add acceptable extionsions in project.properties or any other customisable project file we'd be set for other demands too.

[nikeee]

Was this fixed in #511?

[ScruffR]

Not entirely IMO.

Especially for the part about arbitrary files/extentions

(or some other non-standard extensions). So if we could also provide a way to add acceptable extionsions in project.properties or any other customisable project file we'd be set for other demands too.

I'm also not sure whether #511 is not limited to uploading libraries while this issue is about uploading to the build farm for compilation.

This would require some extra testing.

[nikeee]

I think it looks like it is intended that one can upload more file types: https://github.com/particle-iot/particle-library-manager/blob/master/src/libcontribute.js