From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libcoap: add new package
Date: Wed, 5 Mar 2014 11:37:26 +0100 [thread overview]
Message-ID: <20140305103724.GA2896@omega> (raw)
In-Reply-To: <20140305094854.GD32080@pengutronix.de>
On Wed, Mar 05, 2014 at 10:48:54AM +0100, Michael Olbrich wrote:
> Hi,
>
> On Wed, Mar 05, 2014 at 09:48:47AM +0100, Alexander Aring wrote:
> > I see you applied other patch "libzmq: add new package" already. Is
> > there something wrong with this patch or simple needs a little more time
> > to review? :-)
>
> I need some clarification mostly. You're replacing the whole build-system.
> That's not something I want to maintain inside ptxdist. I can only accept
> that if this will be upstream the next time we update the package in
> ptxdist. So what's the upstream status of these patches?
>
Maintainer don't want to use automake in his buildsystem, I think it
will never go into mainline of libcoap. There is also no mailinglist for
this project, I mailed with the maintainer private.
General problem:
The library buildsystem was made for static linking to a non dynamic
loading operation system.
I can try an alternative instead of reimplemnt the whole buildsystem.
Steps are:
1. Patch libcoap package to add a libcoap.pc file with static paths and
add CFLAGS with -D WITH_POSIX.
2. Compile shared libcoap library with make and -D WITH_POSIX
(There exists a way mainline to compile a shared library)
3. on make install, install it to static path usr/lib/ and
usr/lib/pkgconfig usr/include...
3.1. There is something special on header copy to usr/include:
copy a dummy header for config.h (I hope that should work).
Normally the config.h is created by autoconf and they included it
in every header but no header use config.h information in the header
files (I suppose). So we don't need patch 4/6 (libcoap: remove
include of config.h).
4. copy library, headers into LIBCOAP_PKGDIR.
Something in that way...
I think all option will be end in some hack. I can try to do the
alternative and then we looks if it's better or not, if you are
interested in.
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-03-05 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:40 Alexander Aring
2014-03-05 8:48 ` Alexander Aring
2014-03-05 9:48 ` Michael Olbrich
2014-03-05 10:37 ` Alexander Aring [this message]
2014-03-05 14:20 ` Marc Kleine-Budde
2014-03-30 12:35 Alexander Aring
2014-04-01 14:11 ` Michael Olbrich
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=20140305103724.GA2896@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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