From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH] configure/make basics
Date: Mon, 27 Feb 2012 09:23:31 -0800 [thread overview]
Message-ID: <1330363411.3392.53.camel@aeonflux> (raw)
In-Reply-To: <4F4B9E8C.3080809@vfnet.de>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Hi Jens,
> while hacking on a plugin for mmsd to deal with supl push
> messages, I ran into a few "not so nice" solved things
> in configure.ac / Makefile.am
>
> 1) libtool handling
> libtool configuration is meanwhile done using LT_INIT(options)
> instead of AC_PROC_LIBTOOL and alike
> ==> because of libtool stores some of the configuration
> in the generated libtool shell script, it's reasonable
> to run LT_INIT as late as possible (painfully learned
> while writing and porting c++ software for many OS)
> 2) additional libraries
> do no require explicit libraries (like -lresolv), always
> let a devop in doubt invoke configure with
> LIBS="-lmyspecialwrapper" to wrap between available
> libs/functions and requirements
> See pkgsrc's nbcompat library for example
one patch per email please and all inline. Thanks.
Regards
Marcel
prev parent reply other threads:[~2012-02-27 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 15:17 [PATCH] configure/make basics Jens Rehsack
2012-02-27 17:23 ` Marcel Holtmann [this message]
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=1330363411.3392.53.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/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