Norbert,
I was thinking of gcc-wrapper more as a libreoffice-internal tool like
concat-deps than a external cygwin package.
The Microsoft linker is supported by autoconf so it is handled in
ExternalProject.mk.
Thanks,
Peter
On Wed, Mar 13, 2013 at 5:48 PM, Norbert Thiebaud <nthiebaud@gmail.com>wrote:
On Wed, Mar 13, 2013 at 4:37 PM, Peter Foley <pefoley2@verizon.net> wrote:
I've written a wrapper around MSVC cl.exe for autoconf (see
https://wiki.documentfoundation.org/Development/Gsoc/Ideas#Gcc_like_wrapper_for_MSC_on_cygwin_and_autotools_compatibility
).
The goal of the wrapper is to remove all the custom MSVC logic from the
ExternalProject makefiles and let the packages just use autoconf.
I've uploaded the gcc-wrapper patch to gerrit as well as two example
implementations.
The code was rather quickly hacked together so it may still be buggy.
Is this something that should be integrated into libreoffice?
The wrapper itself, probably not, otherwise you get the usual
bootstrap problem...
but a solution would be to make it avaiable as an external pre-req
like the dozen that Windows already has...
Ideally I suppose, in a cygwin-like package (rpm?) that one could
install in cygwin... just like we already request for 2 dozen of
packages to be installed in cygwin to be able to build...
Norbert
PS: make sure that the wrapper is 'versionable', since I suspect that
some behaviors will depend on the underlying version of the MS
compiler...
PS2: how do you deal with the 'linker' aspect of things ?
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.