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


Hi Bjoern,

On 08/12/16 17:13, Bjoern Michaelsen wrote:
I mean, we could have a tinderbox run "./autogen.sh && make
vs2013-ide-integration" once a week and make it commit the result Visual Studio
solutions to the core repo.

        Sure - although my ideal flow for a (Windows) newbie here would be:

        * download 'something'
        * load file in Visual Studio
        * ctrl-shift-b to build ... <wait>
        * click the green triangle to debug ;-)

        Where of course that 'something' would need to be constructed by some
tinderbox / slave, and (ideally) contain everything not easily buildable
with the IDE already pre-built =)

        Personally I'd see this as an entry mode: once people have the
satisfaction of seeing their work 'working' they can graduate to
installing cygwin, and <insert other pain points>. Clearly there would
be nothing authoritative about it etc.

        Since the instdir/ is standalone and distributable & runnable as-is
there should be no need for make_installer-ness of any kind;

        AFAICS - there -should- also be no need for cygwin, LODE, or anything
else in this world ;-) just a single download.

        Anyhow - just a thought ;-) not volunteering to do the testing,
packaging work for that deliverable ...

        ATB,

                Michael.

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

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.