On Monday, 21 October 2019 at 19:20:04 UTC, Prokop Hapala wrote:
What exactly should I specify to make it link dynamcially and
produce as small binary as possible (without increasing
compilation time) ?
Hi! Sorry, just found your response here. In order to force it to
link dynamically, add
On Wednesday, 1 August 2018 at 15:58:53 UTC, Jacob Shtokolov
wrote:
On Tuesday, 31 July 2018 at 15:19:19 UTC, Dan Barbarito wrote:
Hi all,
I am starting to write a command line tool.
Hi!
First, Vibe.d will increase your binary size because it
contains a lot of unnecessary things inside it.
Thank you for all of the great answers, everyone!
On Tuesday, 31 July 2018 at 15:19:19 UTC, Dan Barbarito wrote:
Hi all,
I am starting to write a command line tool.
Hi!
First, Vibe.d will increase your binary size because it contains
a lot of unnecessary things inside it. So instead of using the
entire vibe.d library, you may point dub to
On Tuesday, 31 July 2018 at 15:19:19 UTC, Dan Barbarito wrote:
Hi all,
I am starting to write a command line tool. So far it is a
small (feature-wise) program but the file size is scaring me.
It's already 13 megabytes, but I would expect it to be much
smaller. Is it because I'm using 3
On 7/31/18 11:19 AM, Dan Barbarito wrote:
Hi all,
I am starting to write a command line tool. So far it is a small
(feature-wise) program but the file size is scaring me. It's already 13
megabytes, but I would expect it to be much smaller. Is it because I'm
using 3 libraries so far? The
Hi all,
I am starting to write a command line tool. So far it is a small
(feature-wise) program but the file size is scaring me. It's
already 13 megabytes, but I would expect it to be much smaller.
Is it because I'm using 3 libraries so far? The libraries are:
mir, vibe.d, and d2sqlite3.
