Am 13.06.19 um 01:31 schrieb brian m. carlson:
> [0] AFAIUI, Windows doesn't have RPATH-like functionality, and from what
> I've read, the same-directory behavior may be going away due to security
> concerns. I don't use Windows, so any solution there is fine as long as
> Dscho is happy.
The solu
Paul Smith writes:
> I assumed that we were discussing providing an _option_ of building
> with shared libraries, rather than removing support for static
> libraries and only supporting shared libraries. The former is the
> typical model in portable projects.
> ...
> So, the answer to most of th
On Thu, 2019-06-13 at 09:51 +0200, Johannes Schindelin wrote:
> Hassles aside, you mentioned Linux and macOS. What about literally
> *all* the other platforms we support? Like AIX, NonStop, HP/UX, etc?
I assumed that we were discussing providing an _option_ of building
with shared libraries, rathe
On 2019-06-12 at 13:57:43, Paul Smith wrote:
> On Tue, 2019-06-11 at 23:48 +, brian m. carlson wrote:
> > Also, some people install Git into their home directories, and a
> > shared library means that they'll have to use LD_LIBRARY_PATH (or
> > equivalent) to run Git.
>
> I don't have strong f
Hi Paul,
On Wed, 12 Jun 2019, Paul Smith wrote:
> On Tue, 2019-06-11 at 23:48 +, brian m. carlson wrote:
> > Also, some people install Git into their home directories, and a
> > shared library means that they'll have to use LD_LIBRARY_PATH (or
> > equivalent) to run Git.
>
> I don't have stro
On Tue, 2019-06-11 at 23:48 +, brian m. carlson wrote:
> Also, some people install Git into their home directories, and a
> shared library means that they'll have to use LD_LIBRARY_PATH (or
> equivalent) to run Git.
I don't have strong feeling about .so's although obviously less disk
space use
On Wed, Jun 12, 2019 at 11:41:10AM +0200, Ævar Arnfjörð Bjarmason wrote:
> On Tue, Jun 11 2019, Elmar Pruesse wrote:
> > The total compiled size of libexec/git-core is currently somewhere
> > around 30 MB. This is largely due to a number of binaries linking
> > statically against libgit.a. For some
On Wed, Jun 12, 2019 at 4:42 PM Ævar Arnfjörð Bjarmason
wrote:
> I.e. we'd just have one git binary, everything else symlinking to that,
> and we'd route to the right program by inspecting argv, which we mostly
> do already.
If I remember correctly libcurl.so startup time was the reason it's
spli
On Tue, Jun 11 2019, Elmar Pruesse wrote:
> Hi!
>
> The total compiled size of libexec/git-core is currently somewhere
> around 30 MB. This is largely due to a number of binaries linking
> statically against libgit.a. For some folks, every byte counts. I
> meddled with the Makefile briefly to ma
On Wed, Jun 12, 2019 at 2:11 PM brian m. carlson
wrote:
>
> On 2019-06-11 at 19:52:18, Elmar Pruesse wrote:
> > Hi!
> >
> > The total compiled size of libexec/git-core is currently somewhere
> > around 30 MB. This is largely due to a number of binaries linking
> > statically against libgit.a. For
On 2019-06-11 at 19:52:18, Elmar Pruesse wrote:
> Hi!
>
> The total compiled size of libexec/git-core is currently somewhere
> around 30 MB. This is largely due to a number of binaries linking
> statically against libgit.a. For some folks, every byte counts. I
> meddled with the Makefile briefly t
Hi!
The total compiled size of libexec/git-core is currently somewhere
around 30 MB. This is largely due to a number of binaries linking
statically against libgit.a. For some folks, every byte counts. I
meddled with the Makefile briefly to make it build and use a libgit.so
instead, which dropp
12 matches
Mail list logo
