The documentation is written in poor english. Review and correction by a native speaker would be great.

I experience this error when I run make:

Makefile.am: required file `./INSTALL' not found
Makefile.am:   `automake --add-missing' can install `INSTALL'

I'm running Ubuntu 12.04

Usually, a git repository contains only sources. Documentation is handled separately.
PDF documents are usually hosted on a website.
Doxygen documentation is rarely checked into the source repository.

Proposals:

• Add a separate repository for generated documents (PDF and doxygen) and/or add a branch gh-pages in this repository (http://pages.github.com/) to setup http://ivilink.github.com with api documentation.
• If source documents for PDF are plain txt files, they can be checked in.
• Remove doc folder from the main repository and move all the sources to root folder.

Additional comments:

It would be great if luxoft provided a full git history, not just "check in version 1", "check in version 2" commits.
Providing only major versions on github is no different than hosting an archive with sources on a website.

I believe this software is open source but it ought to be clear to those who are unfamiliar with the licensing terms and who may want to use the software.

For instance,
https://github.com/Luxoft/iviLink/blob/master/src/samples/linux/Profiles/AuthenticationProfileImpl/CAuthenticationProfileImpl.cpp#L34

include "3rd_party/cryptopp/cryptopp-5.6.1/queue.h"

-I option should be used instead.

Does ivilink use exceptions?

I mean

char *someVar = new char[  0xDEAD ];
strcpy( someVar, "I can fly" );

If new fails, what's going to happen?

Any instruction on how to build ivilink for android is missing.

You don't need a GitHub repo to release sources a few times a year.
GitHub is all about collaboration. It's not just a hosting for your sources.
I don't see much collaboration here.
You could just distribute zipped sources via ivilink.net.

Hello,

Do you have any coding styles?

I see that you've got a couple of styles like

std::list <std::string> ReadFile(const std::string name);

AND

CError NegotiateChannel(std::string tag, UInt32 & channelId);

What is more, sometimes I encounter tabs, sometimes spaces.

Secondly, are there any agreements what should be used for a project? For instance, exception free libraries, pthread as a library from ITC etc.

It's sad that iviLink maintainers decided to check in the generated documentation into source control.
It would be better to handle it differently. For example, it could be generated as a part of the build process.
Or in a separate repository: http://ivilink.github.com/api_doc.html
Also, there is no version in the resulting documentation, which should be added to the Doxyfile.