On 2025-03-19 13:25, Jon Turney via Cygwin-apps wrote:
On 19/03/2025 09:33, Carlo B. via Cygwin-apps wrote:
So, after looking at this a bit, the reason why a debuginfo package isn't
generated is because none of the files are compiled with debug info.
This is due to this line in the cygport:
CXXFLAGS=-D_GNU_SOURCE
Which has the effect of overwriting the "-g" flag (and others) that cygport
wants to supply to the compiler.
This is probably under-documented, but usually you want to append to, rather
than overwrite the compiler flags, e.g.:
CXXFLAGS="${CXXFLAGS} -D_GNU_SOURCE"
With this change, the debuginfo package seems to be generated correctly!
As cygport uses *bash*, you may avoid variable typos by consistently appending
using +=" ", for all flags and any other similar build options that may already
have been set by cygport or inherited classes; for example:
...FLAGS+=" -D..."
^ some white space is required
(BTW: It would also be helpful if this cygport has
BUILD_REQUIRES="mingw64-x86_64-fftw3 mingw64-x86_64-libsamplerate"
so I know what packages to install to build it)
...plus any other libraries or tools that are not installed as dependencies with
the base packages or cygport, so that builds run by Scallywag CI succeed, when
run by pushing your cygport and any patches to your package repo at:
ssh://cyg...@cygwin.com/git/cygwin-packages/<PKG>[.git]
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher but when there is no more to cut
-- Antoine de Saint-Exupéry
