delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Recipient: | geda-user AT delorie DOT com |
DKIM-Signature: | v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h= |
mime-version:in-reply-to:references:content-type:message-id | |
:content-transfer-encoding:from:subject:date:to; s=beta; bh=3WKj | |
HFlyt50WJNk1W+/5BKATPyJWxIFgOPbE7NXbSN0=; b=DVIB1aF1QyzKRsjiWgnq | |
hJ97Ee2B7+OWS8CDKOb2ZphFbnQPkS+xoAOP3gKjGv4HwUDZM9gNQ6AfU0/VCMDu | |
jOuc8QTYhWDEzIMnqkTdUGST8kROk/SfEmiUns5UWosxZYo97TraPJd83as1Fmag | |
q1zsdagRGe4nGuHMEWA8Q7s= | |
Mime-Version: | 1.0 (Apple Message framework v753.1) |
In-Reply-To: | <20130225123922.2588.qmail@stuge.se> |
References: | <a1278e5f88ff58af741935c7c66fe3b4 AT mail DOT theimps DOT com> <kgfk8g$ecn$1 AT ger DOT gmane DOT org> <20130225123922 DOT 2588 DOT qmail AT stuge DOT se> |
Message-Id: | <F3C329AE-FFA7-43F6-94C0-FB884329C143@jump-ing.de> |
From: | Markus Hitter <mah AT jump-ing DOT de> |
Subject: | Re: [geda-user] Building gEDA |
Date: | Tue, 26 Feb 2013 21:19:13 +0100 |
To: | geda-user AT delorie DOT com |
X-Mailer: | Apple Mail (2.753.1) |
Reply-To: | geda-user AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-user AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Am 25.02.2013 um 13:39 schrieb Peter Stuge: > Kai-Martin Knaak wrote: >> Um... >> I always thought, the whole business of ./autogen.sh and ./ >> configure is to >> to check for this kind of dependencies. Who else but those who >> compile >> from git source would need to run the configure script in the >> first place? > > There is significant difference between building from git source > (only done by a small number of people on a small number of systems) > and building from a snapshot or release tarball (done by many more) Do people actually build from tarballs these days? I remember well the days when I compiled dozens of GNU tarballs on AIX and IRIX to get the comfort of Linux. But today I either use a package from the package manager - 99% of the cases - or git directly. Even source code based Linuxes/BSDs have package managers these days! > The actual thing that matters is what is *really* required to build. > > The build process does not in any way interact with packages, so > packages are not relevant. Header files and symbols in libraries are. That's entirely true. Giving a hint in which package a library/header/ tool can be found can't hurt, though. Am 25.02.2013 um 21:03 schrieb Peter Stuge: > I find it completely acceptable > to have "significant barriers" to build from git source. Sorry, no. Any kind of barriers should be avoided as much as possible. > Doing any > kind of cross-platform development, such as gEDA is, along with most > open source, already has "significant barriers" for any developer who > has not participated in such a project before. Can't follow here. configure even checks wether a working compiler is available, it's designed to solve/check everything beyond the simple "./configure && make" term. How does being cross-platform enforce significant barriers? For my part I can't see such a dependency. Also I don't expect READMEs to be read unless the intuitive way to build a package fails. Accordingly, requiring to read the README is sort of a barrier already :-) my $0.02 Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus Hitter http://www.jump-ing.de/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |