simplify rasnet use

[Peter Baumann]

The whole procedure described in ​http://rasdaman.org/wiki/InstallFromSource#rasnetcommunicationprotocol should go into the Makefiles.

[Dimitar Misev]

Alex should create the git submodules structure for these dependencies if I remember correctly?

[Alex Toader]

I was planning on doing this after the release as it requires substantial changes. You usually don't do major changes in beta. Alex's installer can take care of this for now. If you want I can do the changes until Wednesday

[Peter Baumann]

yes, please do implement these changes. Usability is an important acceptance factor.

[Dimitar Misev]

Replying to atoader:

You usually don't do major changes in beta.

Agreed, although rasnet is still optional so it's perhaps not so critical.

[Alex Toader]

I want to create a third_party folder which will contain a folder named grpc which points to the GRPC repo (the folder will be added using git submodules).

I need to build grpc and protobuf (included in grpc's dependencies) and install them to a temporary location.

What should this temporary location be? It needs to exists throughout the build process because I will use it for the include path and library paths needed by rasdaman.

[Alex Toader]

I think that users who want to use raslib will also need access to these libraries. They will link their code against raslib and the libraries of the communication protocol. Any thoughts on how to structure this?

[Peter Baumann]

rasnet conveys tons of compiler warnings which need to be removed. Further, we might suppress the warnings coming from the Google code.

[Alex Toader]

I think the warnings issue should be moved to its own ticket. It will require more than a few hours of work.