On Thursday, 21 January 2016 at 14:03:03 UTC, FreeSlave wrote:
On Thursday, 21 January 2016 at 13:26:15 UTC, W.J. wrote:
On Wednesday, 20 January 2016 at 16:01:11 UTC, Dibyendu
Majumdar wrote:
[...]
Hi,
On Linux you can use 'ldd' to print shared library
dependencies.
On Windows you can use
On Thursday, 21 January 2016 at 13:26:15 UTC, W.J. wrote:
On Wednesday, 20 January 2016 at 16:01:11 UTC, Dibyendu
Majumdar wrote:
Hi,
I am trying to understand the options for distributing a D app
to users. My assumption is that only the shared libraries and
binaries need to be distributed, a
On Wednesday, 20 January 2016 at 16:01:11 UTC, Dibyendu Majumdar
wrote:
Hi,
I am trying to understand the options for distributing a D app
to users. My assumption is that only the shared libraries and
binaries need to be distributed, and I need to include the D
libraries. Is this correct?
T
By default, a binary compiled with D will have the standard
library statically linked in, so all you need to distribute are
other shared libs you choose to use (which might include curl btw
if you use the std.net.curl functions).
But many .exes from D can be distributed alone and expected to
On 21/01/16 5:01 AM, Dibyendu Majumdar wrote:
Hi,
I am trying to understand the options for distributing a D app to users.
My assumption is that only the shared libraries and binaries need to be
distributed, and I need to include the D libraries. Is this correct?
Thanks and Regards
Dibyendu
B
Hi,
I am trying to understand the options for distributing a D app to
users. My assumption is that only the shared libraries and
binaries need to be distributed, and I need to include the D
libraries. Is this correct?
Thanks and Regards
Dibyendu
