Install rules

[pdigiglio]

make install installs the header files in ${CMAKE_INSTALL_PREFIX}/include/YAP with rw-r--r-- permissions, and the shared library libYAP.so in ${CMAKE_INSTALL_PREFIX}/lib with rwxr-xr-x permissions.

Optionally a DESTDIR can be specified at installation-time:

$ make DESTDIR=/home/my_user install

This will install the files in ${DESTDIR}/${CMAKE_INSTALL_PREFIX}.

@greenwald Which permissions should the data/ files have when installed?

[greenwald]

make the data permissions the same as the include permissions.

[pdigiglio]

Should the install target set the YAPDIR environment variable?

It might be useful to have

export YAPDIR=${CMAKE_INSTALL_PREFIX}

I think we shouldn't rely on environment variables (thus we should change the examples and the tests).

[greenwald]

We should exclude the installation of the data files from the full installation (which should only install the headers and lib). Perhaps a custom target, install-data is the best and easiest way to go for the moment.

[greenwald]

So what are the targets that will be available. I gather there will be

• make install-core
• make install-data

But will there also be make install (which should perform the same function as make install-core)? If not, please add it. At the base, what we require is:

• make install (installs the library and headers)
• make install-data (installs the data file)

[pdigiglio]

There is

• make install: installs everything;
• make install/local: I didn't get what it is;
• make install/strip: I didn't get what it is;
• make install-core: installs libYAP.so and headers;
• make install-data: installs the data directory.

I wasn't able to default install to install-core nor to suppress the first three (automatically generated) install rules.

[greenwald]

And there's no way to create our own separate target install-data to install the data and to therefore exclude it from the install target?

Another option would be to somehow exclude the action in install-data if the install location is /usr/local