• Arjan (4/4) Feb 07 2022 In c++ our release builds are build `-O2 -g` and the resulting
• max haughton (2/7) Feb 07 2022 Why build with debug info if you're going to strip it anyway?
• Arjan (5/12) Feb 07 2022 The stripped release binaries are going to the client, when a
• max haughton (3/16) Feb 07 2022 Then yes, you can do that.

Arjan <arjan ask.me.to> writes:

In c++ our release builds are build `-O2 -g` and the resulting 
binaries are stripped with GNU/strip.
Is this also possible with LDC2 generated binaries for D code?
So build D code with `-O2 -g` and then strip the resulting binary?

max haughton <maxhaton gmail.com> writes:

On Monday, 7 February 2022 at 12:16:53 UTC, Arjan wrote:
 In c++ our release builds are build `-O2 -g` and the resulting 
 binaries are stripped with GNU/strip.
 Is this also possible with LDC2 generated binaries for D code?
 So build D code with `-O2 -g` and then strip the resulting 
 binary?

Why build with debug info if you're going to strip it anyway?

Arjan <arjan ask.me.to> writes:

On Monday, 7 February 2022 at 13:14:19 UTC, max haughton wrote:
 On Monday, 7 February 2022 at 12:16:53 UTC, Arjan wrote:
 In c++ our release builds are build `-O2 -g` and the resulting 
 binaries are stripped with GNU/strip.
 Is this also possible with LDC2 generated binaries for D code?
 So build D code with `-O2 -g` and then strip the resulting 
 binary?

 Why build with debug info if you're going to strip it anyway?

The stripped release binaries are going to the client, when a 
problem occurs get a core dump, using the core dump + the 
original binary / symbol gives full debug info off site.

It is common practice.

max haughton <maxhaton gmail.com> writes:

On Monday, 7 February 2022 at 14:20:31 UTC, Arjan wrote:
 On Monday, 7 February 2022 at 13:14:19 UTC, max haughton wrote:
 On Monday, 7 February 2022 at 12:16:53 UTC, Arjan wrote:
 In c++ our release builds are build `-O2 -g` and the 
 resulting binaries are stripped with GNU/strip.
 Is this also possible with LDC2 generated binaries for D code?
 So build D code with `-O2 -g` and then strip the resulting 
 binary?

 Why build with debug info if you're going to strip it anyway?

 The stripped release binaries are going to the client, when a 
 problem occurs get a core dump, using the core dump + the 
 original binary / symbol gives full debug info off site.

 It is common practice.

Then yes, you can do that.

D works in basically exactly the same way C++ does in this regard.