On 3/13/2010 1:36 AM, Roger While wrote:
> gettext supplies libintl.la.
> That file requires libiconv.la.
That is what would be supported by a 'build-depends:' tag -- which is
exactly how that is handled by more powerful package management systems
like rpm, deb, apt, and even ebuild.
The original design of setup.exe was supposed to support this, but it
never has been fleshed out. From setup CVS, inilex.ll:
...
"Binary:" return BINARYPACKAGE;
"Build-Depends:" return BUILDDEPENDS; <<<<<<
"Build-Depends-Indep:" return BUILDDEPENDS; <<<<<<
"Standards-Version:" return STANDARDSVERSION;
"Format:" return FORMAT;
"Directory:" return DIRECTORY;
"Files:" return FILES;
"category:"|"Section:" return CATEGORY;
"Priority:" return PRIORITY;
"requires:" return REQUIRES; <<<<<<
"Depends:" return DEPENDS;
"Pre-Depends:" return PREDEPENDS;
"Recommends:" return RECOMMENDS;
"Suggests:" return SUGGESTS;
"Conflicts:" return CONFLICTS;
"Replaces:" return REPLACES;
"Provides:" return PROVIDES;
...
Note that there are a lot of other interesting items, such as Conflicts,
Replaces, Provides...none of which have any actual 'meat' associated
with them.
> It is not clear to me how one could check for this situation in configure.
You can't -- it is a meta operation, and /should/ be handled by the
package management system.
On linux, the -src.rpm (or .deb) would have a build-depends on the
various -devel packages that you would need. It's a shortcoming of
setup.exe that we can't do that.
The solution is (a) to add that support to setup.exe, and (b) start
moving the build-depends information for individual packages into their
setup.hint files (currently, build-depends are usually -- but not always
-- documented in /usr/share/doc/Cygwin/<pkg>.README
The solution is NOT to overload the runtime requires: field, blurring
the distinction between actual requirements -- without which the app
will refuse to launch at all -- and these other scenarios which are of
interest only to developers ("users" don't run configure).
I'm sure cgf would entertain some refinements to the setup.hint
documentation.
--
Chuck
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
