Recommended build instructions ...

classic Classic list List threaded Threaded
14 messages Options
Michael Meeks-5 Michael Meeks-5
Reply | Threaded
Open this post in threaded view
|

Recommended build instructions ...

Hi there,

    Quick sob-story, my laptop died (RIP), and I urgently needed a new one at the conference. So I bought a Windows 10 thing - new out of the box, and took advantage of the situation to read and follow the instructions from the wiki.

https://wiki.documentfoundation.org/Development/BuildingOnWindows

    Which recommended lode:

https://wiki.documentfoundation.org/Development/lode

    With remarkably little effort I did an impression of a clueless newbie ;-) here are my findings; and I believe we should take some swift action, and get some principles nailed down.


* I was excited about Chocolatey

    I read the website, thought 'wow Windows is getting its act together', then I tried to use it. The downloads complained of not being signed, I ignored that, but still they refused to work - eventually I gave up, and moved on to manual installation.

*  Recommending a known-good Visual Studio

    The LODE page for some reason recommends Visual Studio 2015 - three times, though there is 2013 in the small print. I was to discover many hours later that in fact LibreOffice x86 on the libreoffice-5-2 branch (at least) doesn't compile in this configuration. I was surprised to find out that this is a well known problem later. We should not be documenting and recommending a known-problematic configuration to beginners - even if everyone is rightly excited about moving to the new compiler =)

    => will propose at the ESC that we recommend to beginners only those
       configurations which we know build - ie. have a tinderbox, and CI
       support to keep them working all the time.

    This is somewhat more problematic, since (apparently) installing first 2015 and then 2013 results in a truck-load of other odd behaviors, which are really hard to fix without re-instaling (so the paranoid meme goes ;-)

* Antivirus

    I was broken by McAffe - it broke git - the simple clone failed with a permissions problem. We have a not-very-explicit "turn off AV" messaging but not in the LODE (or devcentral) pages, and we should do that earlier I think; step #1 ;-)

    Anyhow - thought I'd provide my feedback; I hope the solutions are obvious and we can clean this up nicely at least until 2015 is guarenteed to work by CI etc. =)

    HTH,

        Michael.


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Thorsten Behrens-6 Thorsten Behrens-6
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

Michael Meeks wrote:
> * I was excited about Chocolatey
>
Same here -

>     I read the website, thought 'wow Windows is getting its act together',
> then I tried to use it. The downloads complained of not being signed, I
> ignored that, but still they refused to work - eventually I gave up, and
> moved on to manual installation.
>
And indeed the same story - that makes it at least two, let's kill
that section.

>     The LODE page for some reason recommends Visual Studio 2015 - three
> times, though there is 2013 in the small print. I was to discover many hours
> later that in fact LibreOffice x86 on the libreoffice-5-2 branch (at least)
> doesn't compile in this configuration.
>
Can we collectively resource fixing that? I recall a problem, but
forgot the details. Tying us to a particular version seems problematic
to me. Beyond that - yeah, let's fix the onboarding wiki.

>     I was broken by McAffe - it broke git - the simple clone failed with a
> permissions problem. We have a not-very-explicit "turn off AV" messaging but
> not in the LODE (or devcentral) pages, and we should do that earlier I
> think; step #1 ;-)
>
That might need more nuancing perhaps, lest that we make it appear
~impossible for some people to build at all (policy & things).

Cheers,

-- Thorsten

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice

signature.asc (968 bytes) Download Attachment
slacka slacka
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by Michael Meeks-5
Michael Meeks-5 wrote
* I was excited about Chocolatey ... eventually I gave up, and moved on to manual installation.
As did I. If you look at the history all of the Chocolatey info was recently added. It seems to cause more problems than it solves. Should we should move it off into it's own section at the end until it offers a smooth experience?

Michael Meeks-5 wrote
*  Recommending a known-good Visual Studio

     The LODE page for some reason recommends Visual Studio 2015 - three
times, though there is 2013 in the small print.
Again, the VS2015 info was all added with Chocolatey. The old LODE wiki page recommend 2013. Also the main Windows dev page also makes it clear that 2013 is the preferred version.

That said I'd rather see a VS2015 Jenkins or Tinderbox rather than steer people away from it. I've been building both 32/64 VS2015 builds regularly all year long.

Michael Meeks-5 wrote
 * Antivirus
The main Windows dev pages covers this topic thoroughly.

Since you've verified it's a problem, please add McAffe to the list that's already there.


Akash Jain Akash Jain
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by Michael Meeks-5
> *  Recommending a known-good Visual Studio
>
>     The LODE page for some reason recommends Visual Studio 2015 - three
> times, though there is 2013 in the small print. I was to discover many hours
> later that in fact LibreOffice x86 on the libreoffice-5-2 branch (at least)
> doesn't compile in this configuration. I was surprised to find out that this
> is a well known problem later. We should not be documenting and recommending
> a known-problematic configuration to beginners - even if everyone is rightly
> excited about moving to the new compiler =)

Also it is not possible, at the moment, to make a debug build using
Visual Studio 2015. Here is a relevant mail I posted on the list about
the problem:
http://nabble.documentfoundation.org/Debugging-specifics-wrt-visual-studio-td4185447.html

This can also be mentioned on the wiki, so that one can install the
appropriate version of Visual Studio ( and not build with 2015 only to
find that debugging does not work).

Regards,
Akash
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Wols Lists Wols Lists
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by Thorsten Behrens-6
On 09/09/16 18:03, Thorsten Behrens wrote:
>>     I was broken by McAffe - it broke git - the simple clone failed with a
>> > permissions problem. We have a not-very-explicit "turn off AV" messaging but
>> > not in the LODE (or devcentral) pages, and we should do that earlier I
>> > think; step #1 ;-)
>> >
> That might need more nuancing perhaps, lest that we make it appear
> ~impossible for some people to build at all (policy & things).

I believe it is "best practice" to disable AV when installing or
developing software, precisely because it causes so much grief, so may I
suggest something along the lines of

"In line with standard advice on Windows, we recommend disabling AV
while downloading, installing or compiling LibreOffice"

somewhere prominent at the start of the instructions?

That way, we're not telling them they must, just saying that if they
don't then problems are likely to occur and LO is no different from any
other software in that regard.

(And last I looked, I remember AV programs having an option to "disable
until the next reboot".)

Cheers,
Wol
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
slacka slacka
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by Akash Jain
Speaking of wiki build instructions, the IDE instructions for Windows have not worked for almost a year now.
Both the IDE instructions and Windows Instructions say to build with  build with "--enable-debug" and then "make vs2013-ide-integration".  This results in the following error:

cd E:/core && (LC_MESSAGES=C E:/lode/opt/bin/make cmd="E:/cygwin/home/Hearthstone/lode/opt/bin/make -npf Makefile.gbuild all" cmd || true) | E:/core/bin/gbuild-to-ide --ide vs2013

make[1]: *** [cmd] Error 127

According this thread, You need an old version of make.

Could someone please verify these instructions, and put them on the wiki with a *working* download location? None of the versions of make that I was able to find work with the script in that thread.
Juergen Funk Mailinglist Juergen Funk Mailinglist
Reply | Threaded
Open this post in threaded view
|

AW: Recommended build instructions ...

The other problem with Visual Studio Project file is, some projects included not completely or are missing complete

With that solution
http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-tp4140307p4140799.html
 
I don't now is the make wrong or the python-script

juergen
________________________________________
Von: LibreOffice <[hidden email]> im Auftrag von slacka <[hidden email]>
Gesendet: Montag, 12. September 2016 23:08
An: [hidden email]
Betreff: Re: Recommended build instructions ...

Speaking of wiki build instructions, the IDE instructions for Windows have
not worked for almost a year now.
Both the  IDE instructions
<https://wiki.documentfoundation.org/Development/IDE#Microsoft_Visual_Studio>
and  Windows Instructions
<https://wiki.documentfoundation.org/Development/BuildingOnWindows#Microsoft_Visual_Studio_Project_Integration>
say to build with  build with "--enable-debug" and then "make
vs2013-ide-integration".  This results in the following error:

cd E:/core && (LC_MESSAGES=C E:/lode/opt/bin/make
cmd="E:/cygwin/home/Hearthstone/lode/opt/bin/make -npf Makefile.gbuild all"
cmd || true) | E:/core/bin/gbuild-to-ide --ide vs2013

make[1]: *** [cmd] Error 127

According this thread
<http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-tp4140307p4140941.html>
, You need an old version of make.

Could someone please verify these instructions, and put them on the wiki
with a *working* download location? None of the versions of make that I was
able to find work with the script in that thread.




--
View this message in context: http://nabble.documentfoundation.org/Recommended-build-instructions-tp4193014p4193353.html
Sent from the Dev mailing list archive at Nabble.com.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
jan iversen jan iversen
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by slacka
I have added a red mine, so everybody can follow the progress.

https://redmine.documentfoundation.org/issues/2057

rgds
jan I.


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
jan iversen jan iversen
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

In reply to this post by Juergen Funk Mailinglist

> On 13 Sep 2016, at 08:45, Juergen Funk Mailinglist <[hidden email]> wrote:
>
> The other problem with Visual Studio Project file is, some projects included not completely or are missing complete
This is a known challenge. the current gbuild_to_ide was not meant to enable a complete make in VS, but merely to look at the sources and help with debugging.

There are open BZ:
https://bugs.documentfoundation.org/show_bug.cgi?id=96020
https://bugs.documentfoundation.org/show_bug.cgi?id=96021

Patches are very welcome.

The general idea is to update/replace the current script to include all parts of libreoffice, so theoretically it would be possible to build LO from within VS (and other IDE).

If you have time, I am happy to assist.

rgds
jan I.


_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
slacka slacka
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

Is the  "make vs2013-ide-integration" script working for anyone? With a clean Win 10 install + VS 2013 + LODE, I always get:
make[1]: *** [cmd] Error 127

From,
http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-tp4140307p4140941.html

"The "make version 4.0" do it wrong, I build ONLY the VS-Solution with "make version 3.82"
The size is 517.746 Bytes when you have trouble to found, call me, I have forget where I downloaded."

Lode used to download 3.82, but now it downloads 4.0. So new users are out of luck.

Does anyone has a version of make that works with make vs2013-ide-integration? If so, could you please share it on a cloud storage service?
Bjoern Michaelsen Bjoern Michaelsen
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

Hi,

On Wed, Sep 14, 2016 at 01:23:46PM -0700, slacka wrote:
> Does anyone has a version of make that works with make
> vs2013-ide-integration? If so, could you please share it on a cloud storage
> service?

Clinging to ancient toolchains isnt sustainable, Better: Adapt the script to
work with current versions of make.

Best,

Bjoern
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
jan iversen jan iversen
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...


> On 14 Sep 2016, at 22:30, Bjoern Michaelsen <[hidden email]> wrote:
>
> Hi,
>
> On Wed, Sep 14, 2016 at 01:23:46PM -0700, slacka wrote:
>> Does anyone has a version of make that works with make
>> vs2013-ide-integration? If so, could you please share it on a cloud storage
>> service?
>
> Clinging to ancient toolchains isnt sustainable, Better: Adapt the script to
> work with current versions of make.
Then it would be a lot better to not only adapt it, but also finalise the script so it includes all targets (current version misses 7 targets and all java).

rgds
jan I.

>
> Best,
>
> Bjoern
> _______________________________________________
> LibreOffice mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/libreoffice

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Bjoern Michaelsen Bjoern Michaelsen
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

Hi,

On Thu, Sep 15, 2016 at 08:08:07AM +0200, Jan Iversen wrote:
> > Clinging to ancient toolchains isnt sustainable, Better: Adapt the script to
> > work with current versions of make.
> Then it would be a lot better to not only adapt it, but also finalise the
> script so it includes all targets (current version misses 7 targets and all
> java).

Sure, it cant always be improved, but that is optional[1]. OTOH, I would expect
those using the IDE stuff on Windows to also maintain it themselves and keeping it
up-to-date without too much fuzz. Lets punt this to the ESC in case there are
fundamental issues, unless there are concrete technical questions.

Best,

Bjoern

[1] Feel free to make that an EasyHack.
_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice
Tor Lillqvist-2 Tor Lillqvist-2
Reply | Threaded
Open this post in threaded view
|

Re: Recommended build instructions ...

On 15 September 2016 at 10:55, Bjoern Michaelsen <[hidden email]> wrote:
I would expect
those using the IDE stuff on Windows to also maintain it themselves 

I doubt it could be said any more clearly that the IDE stuff should not even be mentioned to newbies then.

---tml

_______________________________________________
LibreOffice mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/libreoffice