Re: commit: link statically the release version on vc++

Hi Tomas, Jordi,

IIRC, MSFT doesn't like people restributing the DLLs
in question. KJD has been linking to the MSVC DLLs for
a while now from http://abiword.pchasm.org.

I'm against this static linking. The resulting binary
is bigger, and for what? Working on WinNT 4 without
having to download additional DLLs? Hasn't Microsoft
stopped supporting it?

Tell me again why we should care *this* much about
that obsolete, unsupported platform?

Best,
Dom

--- Tomas Frydrych <tomasfrydrych@yahoo.co.uk> wrote:

>
> Hi Jordi,
>
> I do not particularly like linking the runtimes in
> statically; would it
> not be better to provide the libs on the download
> side for those who do
> not have them?
>
> Tomas
>
> Jordi Mas wrote:
> >
> > Hi folks,
> >
> > Link statically the release version when compiling
> on vc++. Abiword was
> > unable to run on old Windows systems like Wint 4.0
> - BTW, also known as
> > the 'child that nobody wanted. We were requiring
> the Visual C++ runtime
> > installed and we are not packing it.
> >
> >
> > cvs commit: Examining .
> > CVS:
>
----------------------------------------------------------------------
> > CVS: Enter Log. Lines beginning with `CVS:' are
> removed automatically
> > CVS:
> > CVS: Committing in .
> > CVS:
> > CVS: Modified Files:
> > CVS: win32.mk
> > CVS:
>
----------------------------------------------------------------------
> >
> > Note: Please, BACKPORT to STABLE
>

                
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - What will yours do?
http://my.yahoo.com
Received on Wed Feb 2 22:37:44 2005