bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: eggert@cs.ucla.edu
Cc: bug-gnulib@gnu.org, bruno@clisp.org
Subject: Re: can't compile `stdlib.h` on mxe
Date: Sun, 23 May 2021 05:30:25 +0000 (UTC)	[thread overview]
Message-ID: <20210523.073025.334095998879999271.wl@gnu.org> (raw)
In-Reply-To: <7216338d-a979-3d7f-c8e1-3bf108f65cae@cs.ucla.edu>


>> It doesn't – it is an auto-generated Qt file.  However, the file
>> starts
>> with
>> ```
>> #include <memory>
>> #include "ddlineedit.h"
> 
> You could instead compile a file ddlineedit.config-moc.cpp, with the
> following contents:
> 
> #include <config.h>
> #include "ddlineedit.moc.cpp"

Yeah, this came to my mind, too, thanks!  However, I've now
implemented the following rule in my `Makefile.am` file, which seems
to work fine.

```
SUFFIXES = .moc.cpp .h

moc_verbose = $(moc_verbose_@AM_V@)
moc_verbose_ = $(moc_verbose_@AM_DEFAULT_V@)
moc_verbose_0 = @echo "  MOC     " $@;

.h.moc.cpp:
	$(moc_verbose){ \
	  echo '#include <config.h>'; \
	  $(MOC) ... $< ; \
	} > $@.tmp
	@mv $@.tmp $@
```


    Werner

      reply	other threads:[~2021-05-23  5:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 10:03 can't compile `stdlib.h` on mxe Werner LEMBERG
2021-05-22 12:25 ` Bruno Haible
2021-05-22 12:45   ` Werner LEMBERG
2021-05-22 14:32     ` Bruno Haible
2021-05-22 17:57       ` Werner LEMBERG
2021-05-22 18:39       ` Paul Eggert
2021-05-23  5:30         ` Werner LEMBERG [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=20210523.073025.334095998879999271.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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).