Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On Thu, 2010-10-21 at 21:19 +0100, Martin Gallwey wrote:
Hi there!

Just working further on getting a working build up and running, there
are a bunch of files needed to get a build running, namely, these?

Looking for /cygdrive/c/lo/src/msvcr80.dll ...  ok
Looking for /cygdrive/c/lo/src/msvcp80.dll ...  ok
Looking for /cygdrive/c/lo/src/Microsoft.VC80.CRT.manifest ...  ok
Looking for /cygdrive/c/lo/src/msvcr71.dll ...  ok
Looking for /cygdrive/c/lo/src/gdiplus.dll ... ok

With the exception of the .manifest file, these are all distributed
with the OOo download - would it be possible to put a tarball or zip
of these files up on libreoffice.org and have the build process
download and unpack them as part of the build, or is there some
redistribution licensing foo going on here?

It's a bit confusing to me. Seems you can distribute them along with an
app you write when you have the license to the full version of the
compiler ?, so it would seem to be possible. Probably need to get the
canonical EULA text for them to have a real idea if its possible or not.

And you can also download some them at least from the msdn websites as
well. and I see that http://kegel.com/wine/winetricks has a script which
downloads these from known locations and runs their installers. I would
*imagine* that it would be ok to do that anyway, i.e. a script that
downloads the installers, runs them and let the end-user click-through
any relevant EULAs ?

C.


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.