From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] doxygen
Date: Sat, 17 Oct 2020 15:43:52 +0200 [thread overview]
Message-ID: <87a6wldl2f.fsf@Rainer.invalid> (raw)
In-Reply-To: <588f484e-9768-4844-51f6-2a4593194705@cornell.edu> (Ken Brown's message of "Sun, 11 Nov 2018 22:38:23 +0000")
Ken Brown writes:
> There's no need for a new release at the moment, but I'm attaching the cygport
> file I would use if there were. It differs in only very minor ways from the
> current cygport file (also attached).
For your problem with the debuginfo that we've briefly discussed on IRC:
It turns out I had exactly the same problem before, for exactly the same
reason (Qt moc-generated interface headers) and the same fix works just
as well for doxygen:
CFLAGS+=" -femit-struct-debug-reduced"
That gets you debuginfo packages for both architectures (I didn't have
graphviz installed when building the package locally, but I doubt it
makes a difference for this issue). I doubt anyone is going to notice
the difference due to the less detailed debugging information… :-)
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2020-10-17 13:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 22:38 Ken Brown
2018-11-11 22:42 ` Marco Atzeri
2018-11-12 14:12 ` Andrew Schulman
2018-11-12 14:17 ` Andrew Schulman
2020-10-17 13:43 ` Achim Gratz [this message]
2020-10-17 16:44 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2012-09-29 8:33 David Stacey
2012-09-29 11:00 ` marco atzeri
2012-09-30 0:02 ` Andrew Schulman
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=87a6wldl2f.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.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).