comment #8:

> Nothing personal - usefulness of "hard coded path" for Android and Windows is lie.

This is not a lie.

> Build tools are for general use not for personal one.

GNU Libtool is available for personal use.

> I'm sure that personal environment could be setup do not require hard coded paths.

This assumption and other generalisations that would limit the usage of GNU Libtool is not helpful or productive. Please refrain from opening a new issue on this until proper documentation and arguments can be provided that are not personally offensive to maintainers and contributers of GNU Libtool.

> Goal of build tools is to help package manager(build engineer) to prepare installation.

No, that is not the only goal. Installation by individual users, on their own machines, is a goal of the GNU projects too. See:

• In https://www.gnu.org/prep/standards/html_node/DESTDIR.html, it is allowed to not specify DESTDIR on the 'make install' command line.

• In https://www.gnu.org/prep/standards/html_node/Standard-Targets.html, the 'uninstall' target would not be specified if package managers were the only audience.

> "Make sense" in this context is just a lie.

You should not drift into personal offense.

> Applications(programs) could be installed in any location(path)!

You seem to assume that programs are always meant to be installed on a different machine than on the one it was built.

This is not the case. The GNU project strives to make software modifiable and installable by individual users. Such users often build a package in order to use it only on that machine. In this situation, it does make sense to use hardcoded paths. (Both on Windows and on Android.)

> One recent commit broke Android build.

Nope. This commit of mine was explained in https://lists.gnu.org/archive/html/libtool-patches/2023-09/msg00000.html

There are different environments on Android, as explained in https://lists.gnu.org/archive/html/bug-gnulib/2022-12/msg00100.html .

A statement like "Note that on Android and MIcrosoft Windows must not hard code any paths." is not helpful.

In the Android environment I am using, translating -rpath options to RUNPATH properties is mandatory.

If you are in an Android environment where RUNPATH options are not adequate, either pass '--disable-rpath' to the configure program, or find a way to reliably distinguish the two kinds of environments.

this report lacks detailed (or really, any) information.  the git commit lacks detailed information, and the author e-mail is set to nonsense.