Hello,
I am writing some software to streamline source code
installations for packages built with the autotools,
and manage such installations.
http://www.gnu.org/software/sourceinstall
I found that tcl is difficult to streamline in all
situations, only because tcl installation does not, by
default, install the private headers (with the possible
exception of MacOSX with certain configure options)
A separate custom command like:
make install-private-headers
seems required.
This breaks the common configure, make, make install
pattern, and makes it impossible to automate successive
installations of extensions (most notably tk) in all
situations, for example when the previous sources of
tcl are not available, or in a different location.
I would suggest a couple of alternatives to make tcl
and its extensions easier to streamline:
1) provide a configure option to enable/disable
installation of private headers.
http://www.gnu.org/software/autoconf/manual/autoconf-2.57/html_mono/autoconf.html#SEC131
2) unconditionally add install-private-headers to the
INSTALL_TARGETS in Makefile.in .
Should you opt for 1), I could implement the change
myself and offer you a patch.
Thank you for considering my feature request.
Claudio Fontana
Logged In: YES
user_id=790036
I noticed I posted anonymously (at least as far as the
account goes). Here is the originating account.
Logged In: YES
user_id=72656
pleaes provide an option (1) patch.
Logged In: YES
user_id=90580
as noted, we already install private headers on 'make
install' when tcl & tk are configured with
--enable-framework, by setting
EXTRA_INSTALL=install-private-headers
in configure.in, duplicating this is all that would be
required to implement a new configure option as in (1)
Logged In: YES
user_id=72656
Originator: NO
I think we need a general option 1. This wouldn't effect --enable-framework for OS X.
install-private-headers exists in 8.5+