From: Bruno Haible <bruno@clisp.org>
To: Ergus <spacibba@aol.com>
Cc: bug-gnulib@gnu.org
Subject: Re: Any experience with cmake?
Date: Sun, 01 Sep 2019 11:26:42 +0200 [thread overview]
Message-ID: <37320042.WUxIxUdJPH@omega> (raw)
In-Reply-To: <20190901072036.554puxwswfep3in3@Ergus>
Ergus wrote:
> After reading the thread I see that there is a workaround to generate a
> .a and get the headers with the --create-testdir option.
Yes.
> Could you provide a basic configure.am content file to generate the .a
> or the basic steps.
No. You have to read the documentation by yourself.
Bruno
prev parent reply other threads:[~2019-09-01 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 9:22 Any experience with cmake? Ergus
2019-08-30 13:41 ` Bruno Haible
2019-09-01 7:20 ` Ergus
2019-09-01 9:26 ` Bruno Haible [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37320042.WUxIxUdJPH@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=spacibba@aol.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).