Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] openssl: convert	to	Makefile.autotools.in and bump version to 0.9.8g
Date: Wed, 13 Aug 2008 07:39:18 +0200	[thread overview]
Message-ID: <1218605958.12416.6.camel@localhost> (raw)
In-Reply-To: <20080813032408.GA1773@cloud.net.au>

On Wed, 2008-08-13 at 13:24 +1000, Hamish Moffatt wrote:
> On Tue, Aug 12, 2008 at 02:03:31PM +0200, Hans-Christian Egtvedt wrote:
> > This patch converts building of OpenSSL to use Makefile.autotools.in and bumps
> 
> OpenSSL doesn't use autotools though, so is this a good idea?
> 
> > +$(OPENSSL_TARGET_CONFIGURE):
> > +	(cd $(OPENSSL_DIR); \
> > +		$(TARGET_CONFIGURE_ARGS) \
> > +		$(TARGET_CONFIGURE_OPTS) \
> > +		./Configure \
> > +			linux-$(OPENSSL_TARGET_ARCH) \
> > +			--prefix=/usr \
> > +			--openssldir=/usr/lib/ssl \
> > +			threads \
> > +			shared \
> > +			no-idea \
> > +			no-mdc2 \
> > +			no-rc5 \
> > +			zlib-dynamic \
> >  	)
> 
> Once you've overriden the CONFIGURE stage, is there much benefit left in
> using Makefile.autotools.in?
> 

The Makefile is smaller now, and IMHO easier to read.

Installation of man pages, info pages and header/development works
better now.

I though the autotools was not purely for autotools stuff, but a way to
make every package simpler to read and install in a more general way?

-- 
With kind regards,
Hans-Christian Egtvedt, Applications Engineer

  reply	other threads:[~2008-08-13  5:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-12 12:03 [Buildroot] [PATCH v2 1/1] openssl: convert to Makefile.autotools.in and bump version to 0.9.8g Hans-Christian Egtvedt
2008-08-13  3:24 ` Hamish Moffatt
2008-08-13  5:39   ` Hans-Christian Egtvedt [this message]
2008-09-11 11:58     ` Hans-Christian Egtvedt
2008-09-11 13:06       ` Hamish Moffatt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1218605958.12416.6.camel@localhost \
    --to=hans-christian.egtvedt@atmel.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox