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


I don't understand.

-----Original Message-----
From: LibreOffice [mailto:libreoffice-bounces@lists.freedesktop.org] On Behalf Of Michael Meeks
Sent: Thursday, September 18, 2014 4:36 PM
To: nicholas ferguson
Cc: 'libreoffice'; havlicek.honza@gmail.com
Subject: Re: vs2012-ide-integration

Hi Nicholas,

On Thu, 2014-09-18 at 08:45 -0400, nicholas ferguson wrote:
I built in Visual Studio, using native compilers…modules sc and cui
and all of their dependencies. This build is separate from libreoffice
make files and cygwin.  It doesn’t require references to make files or
cygwin.

        I love the idea; anything to make it easier to build on Windows and
remove the cygwin grief: I feel your pain.

If I send you my notes, could you tweak your vs2012-ide-integration,
to a vs2012native-ide-integration ( or any name you choose) so that we
could generate those projects?  

        Well; the best way is to send a patch of your own. We love patches =)
developers talk code really. I suspect if you start something there you
may find people intersted in playing with it with you & chipping away at
the problem.

        ATB,

                Michael.

-- 
 michael.meeks@collabora.com  <><, Pseudo Engineer, itinerant idiot

_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice




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.