On Fri, 18 Nov 2011 12:12:33 +
Philip Ashmore wrote:
> On 18/11/11 00:07, Neil Williams wrote:
> > On Thu, 17 Nov 2011 20:01:42 +
> > Philip Ashmore wrote:
> >
> >> , presuming they are even installed or the user downloaded (the matching
> >> version of) them.
> > apt-get source - it alw
On 18/11/11 00:07, Neil Williams wrote:
On Thu, 17 Nov 2011 20:01:42 +
Philip Ashmore wrote:
On 17/11/11 14:56, Neil Williams wrote:
The path doesn't matter that much, as long as the debugger can find a
filename which at least matches the end of the path. i.e. work
backwards and use the b
On Thu, 17 Nov 2011 20:01:42 +
Philip Ashmore wrote:
> On 17/11/11 14:56, Neil Williams wrote:
> > The path doesn't matter that much, as long as the debugger can find a
> > filename which at least matches the end of the path. i.e. work
> > backwards and use the best match. This isn't down to
On 17/11/11 14:56, Neil Williams wrote:
On Thu, 17 Nov 2011 13:11:08 +
Philip Ashmore wrote:
While useful, debug symbolsonlyhelp so much.
On some other distributions the debugging symbols package includes the source
code
and kdbg integration so that kdbg can prompt you to download the dbg
On Thu, 17 Nov 2011 13:11:08 +
Philip Ashmore wrote:
> While useful, debug symbolsonlyhelp so much.
> On some other distributions the debugging symbols package includes the source
> code
> and kdbg integration so that kdbg can prompt you to download the dbg package
> while
> you're debuggin
On 17/11/11 12:19, Simon McVittie wrote:
On Thu, 17 Nov 2011 at 13:00:40 +0100, Malte Forkel wrote:
- What do you mean by
Don't strip in the upstream build. Just don't. Ever.
Is it that any stripping should be initiated from debian/rules, but
should never be performed by the upstream Makefil
On Thu, 17 Nov 2011 at 13:00:40 +0100, Malte Forkel wrote:
> - What do you mean by
> > Don't strip in the upstream build. Just don't. Ever.
> Is it that any stripping should be initiated from debian/rules, but
> should never be performed by the upstream Makefiles?
Always build with -g, and never
Thanks for your help, guys!
Now that I (hopefully) understand the Debian approach to providing
debugging information, its obvious why I didn't find any useful
information before: My questions were wrong.
There are two questions which I'd still like to ask:
- Is there any summary on how to provid
On Tue, 15 Nov 2011 at 19:02:48 +, Neil Williams wrote:
> Fix the rest of the flags. In most cases, what you're thinking of as
> the "release" build may actually contain debug symbols which dh_strip
> would then put into a dbg package. What matters (the only thing
> which matters) is exactly wh
On Tue, 15 Nov 2011 19:12:10 +0100
Malte Forkel wrote:
> I need your advise on how to deal with the way Debian packages the debug
> version of Qt libraries.
Debugging symbols exist in the libqt4-dbg package.
When building your own code, it is just a case of ensuring that the
flags are passed to
Hi,
I need your advise on how to deal with the way Debian packages the debug
version of Qt libraries.
I'm trying to package an existing software that includes a small Qt
application. The software is not using autotools or qmake but fixed
Makefiles. Building the release version is accomplished by
11 matches
Mail list logo
