remarks about dev tools

I think that there is some points to improve about the differents
development tools.

Recursive makefiles:
Install feature:
-make install wants to copy all files in /x86/… but it’s absolutely
useless to only copy files to /x86. they have to belong to a package.
issue: modifying INSTALL_ROOT_EX and INSTALL_ROOT_SO between include
qmacros.mk and include qtarget.mk.
-problem while installing headers, INSTALL_DIR doesn’t exist for
headers, make install try to copy them to /usr/include, a read only
filesystem.
issue: modifying INSTALL_ROOT_HDR between include qmacros.mk and include
qtarget.mk.
-it seems that nothing is foreseed to install documentations (help
files, man…).

addvariant:
-with or without -c, advariant look for ci. I think that it’s not what
is explained in the use file.
-as you now use vcs, ci is not the correct command and doesn’t exist.
-it creates RCS directories which is not correct for the cvs.

Regards,
Alain.

Alain Bonnefoy wrote:

I think that there is some points to improve about the differents
development tools.

Recursive makefiles:
Install feature:
-make install wants to copy all files in /x86/… but it’s absolutely
useless to only copy files to /x86. they have to belong to a package.
issue: modifying INSTALL_ROOT_EX and INSTALL_ROOT_SO between include
qmacros.mk and include qtarget.mk.
-problem while installing headers, INSTALL_DIR doesn’t exist for
headers, make install try to copy them to /usr/include, a read only
filesystem.
issue: modifying INSTALL_ROOT_HDR between include qmacros.mk and include
qtarget.mk.
-it seems that nothing is foreseed to install documentations (help
files, man…).

addvariant:
-with or without -c, advariant look for ci. I think that it’s not what
is explained in the use file.
-as you now use vcs, ci is not the correct command and doesn’t exist.
-it creates RCS directories which is not correct for the cvs.

Regards,
Alain.

In fact, I think that make install is really done to prepare a directory
tree for packaging.

Alain.