Error building Visual Studio 2013 project file for LibreOffice on Windows

classic Classic list List threaded Threaded
10 messages Options
Jesper Hertel Jesper Hertel
Reply | Threaded
Open this post in threaded view
|

Error building Visual Studio 2013 project file for LibreOffice on Windows

Hi,

I just tried building LibreOffice for 32-bit Windows on a 64-bit Windows 7 Home Premium machine using Visual Studio 2013 Community Edition. 

I have never built LibreOffice before, and I have carefully followed the instructions from https://wiki.documentfoundation.org/Development/BuildingOnWindows and used all the recommended settings and paths. My Cygwin is 64-bit and the used Java JDK is 32-bit. 

My autogen.input for building LibreOffice is this:

--with-parallelism=2
--disable-odk
--with-junit=/cygdrive/c/sources/junit-4.10.jar
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.4
--with-jdk-home=/cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31
--enable-pch
--disable-ccache
--disable-activex
--disable-atl

and I ran the build from the Cygwin bash shell using this command:

./autogen.sh && /opt/lo/bin/make 

with current directory being

/cygdrive/c/sources/libo-core

which is the root of the tree cloned from git://gerrit.libreoffice.org/core.

As instructed, I built directly to the source tree to get Visual Studio integration.

After the first attempted builds failed, I pulled a more recent master that didn't fail on Tinkerbox, and I think the build succeeded then. There were no errors, but there were also no "Build successful" message or similar in the end. The output just ended with this:

[build SLC] sw
[build SLC] libreoffice
[build SLC] loaded modules: UnoControls accessibility accessories android animations apache-commons apple_remote avmedia basctl basebmp basegfx basic bean beanshell binaryurp boost bridges canvas chart2 clew cli_ure clucene codemaker coinmp collada2gltf comphelper configmgr connectivity cppcanvas cppu cppuhelper cppunit cpputools cui curl dbaccess desktop drawinglayer dtrans editeng embeddedobj embedserv eventattacher expat extensions external extras filter firebird forms formula fpicker framework glew glm graphite helpcompiler hsqldb hunspell hwpfilter hyphen i18nlangtag i18npool i18nutil icu idl idlc instsetoo_native iojavaunohelper jfreereport jpeg-turbo jurt jvmaccess jvmfwk l10ntools lcms2 libabw libcdr libcmis libebook libetonyek libexttextcat libfreehand libgltf liblangtag libmspub libmwaw libodfgen liborcus libpagemaker libpng librelogo libreoffice libreofficekit librevenge libvisio libwpd libwpg libwps libxml2 libxmlsec libxslt lingucomponent linguistic lotuswordpro lpsolve mdds more_fonts msc-externals mythes neon nss o3tl offapi officecfg oovbaapi ooxopencl opencollada openssl package poppler postgresql postprocess python3 pyuno qadevOOo readlicense_oo redland registry remotebridges reportbuilder reportdesign rhino ridljar rscsal salhelper sax sc scaddins sccomp scp2 scripting sd sdext setup_native sfx2 shell slideshow smoketest solenv soltools sot starmath stoc store svgio svl svtools svx sw swext sysui test testtools toolkit tools tubes ucb ucbhelper ucpp udkapi unodevtools unoidl unoil unotest unotools unoxml ure uui vbahelper vcl vigra winaccessibility wizards writerfilter writerperfect xmerge xmlhelp xmloff xmlreader xmlscript xmlsecurity zlib

But after that, it was possible to start LibreOffice Dev using C:\sources\libo-core\instdir\program\soffice.exe, so I guess the build was successful???

Then I tried to build the Visual Studio 2013 solution file using
/opt/lo/bin/make vs2013-ide-integration
with current directory being /cygdrive/c/sources/libo-core.

That gave me this entire output:

cd C:/sources/libo-core && (LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/bin/make -npf Makefile.gbuild all" cmd || true) | C:/sources/libo-core/bin/gbuild-to-ide --ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:

After that, the LibreOffice.sln file is 353 bytes and only contains this:

Microsoft Visual Studio Solution File, Format Version 12.00
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Unit Tests|Win32 = Unit Tests|Win32
Integration tests|Win32 = Integration tests|Win32
Build|Win32 = Build|Win32
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
EndGlobalSection
EndGlobal

and there are no other recently created *.sln files in the entire source/build directory tree.

The error from make (Error 127) is not so helpful and gives me no clue to what is wrong.

Does anybody know what could be wrong? 

I would really like to be able to use the comfort of Visual Studio to browse around the source code.

Best regards,
Jesper


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

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

I tried running make with the --debug parameter, and that gave this output, if that is helpful:

$ /opt/lo/bin/make --debug vs2013-ide-integration
GNU Make 4.0
Built for Windows32
Copyright (C) 1988-2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
GNU Make 4.0
Built for Windows32
Copyright (C) 1988-2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Updating goal targets....
 File 'vs2013-ide-integration' does not exist.
Must remake target 'vs2013-ide-integration'.
cd C:/sources/libo-core && (LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/
bin/make -npf Makefile.gbuild all" cmd || true) | C:/sources/libo-core/bin/gbuild-to-ide -
-ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:
Successfully remade target file 'vs2013-ide-integration'.


Jesper

2015-02-16 20:40 GMT+01:00 Jesper Hertel <[hidden email]>:
Hi,

I just tried building LibreOffice for 32-bit Windows on a 64-bit Windows 7 Home Premium machine using Visual Studio 2013 Community Edition. 

I have never built LibreOffice before, and I have carefully followed the instructions from https://wiki.documentfoundation.org/Development/BuildingOnWindows and used all the recommended settings and paths. My Cygwin is 64-bit and the used Java JDK is 32-bit. 

My autogen.input for building LibreOffice is this:

--with-parallelism=2
--disable-odk
--with-junit=/cygdrive/c/sources/junit-4.10.jar
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.4
--with-jdk-home=/cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31
--enable-pch
--disable-ccache
--disable-activex
--disable-atl

and I ran the build from the Cygwin bash shell using this command:

./autogen.sh && /opt/lo/bin/make 

with current directory being

/cygdrive/c/sources/libo-core

which is the root of the tree cloned from git://gerrit.libreoffice.org/core.

As instructed, I built directly to the source tree to get Visual Studio integration.

After the first attempted builds failed, I pulled a more recent master that didn't fail on Tinkerbox, and I think the build succeeded then. There were no errors, but there were also no "Build successful" message or similar in the end. The output just ended with this:

[build SLC] sw
[build SLC] libreoffice
[build SLC] loaded modules: UnoControls accessibility accessories android animations apache-commons apple_remote avmedia basctl basebmp basegfx basic bean beanshell binaryurp boost bridges canvas chart2 clew cli_ure clucene codemaker coinmp collada2gltf comphelper configmgr connectivity cppcanvas cppu cppuhelper cppunit cpputools cui curl dbaccess desktop drawinglayer dtrans editeng embeddedobj embedserv eventattacher expat extensions external extras filter firebird forms formula fpicker framework glew glm graphite helpcompiler hsqldb hunspell hwpfilter hyphen i18nlangtag i18npool i18nutil icu idl idlc instsetoo_native iojavaunohelper jfreereport jpeg-turbo jurt jvmaccess jvmfwk l10ntools lcms2 libabw libcdr libcmis libebook libetonyek libexttextcat libfreehand libgltf liblangtag libmspub libmwaw libodfgen liborcus libpagemaker libpng librelogo libreoffice libreofficekit librevenge libvisio libwpd libwpg libwps libxml2 libxmlsec libxslt lingucomponent linguistic lotuswordpro lpsolve mdds more_fonts msc-externals mythes neon nss o3tl offapi officecfg oovbaapi ooxopencl opencollada openssl package poppler postgresql postprocess python3 pyuno qadevOOo readlicense_oo redland registry remotebridges reportbuilder reportdesign rhino ridljar rscsal salhelper sax sc scaddins sccomp scp2 scripting sd sdext setup_native sfx2 shell slideshow smoketest solenv soltools sot starmath stoc store svgio svl svtools svx sw swext sysui test testtools toolkit tools tubes ucb ucbhelper ucpp udkapi unodevtools unoidl unoil unotest unotools unoxml ure uui vbahelper vcl vigra winaccessibility wizards writerfilter writerperfect xmerge xmlhelp xmloff xmlreader xmlscript xmlsecurity zlib

But after that, it was possible to start LibreOffice Dev using C:\sources\libo-core\instdir\program\soffice.exe, so I guess the build was successful???

Then I tried to build the Visual Studio 2013 solution file using
/opt/lo/bin/make vs2013-ide-integration
with current directory being /cygdrive/c/sources/libo-core.

That gave me this entire output:

cd C:/sources/libo-core && (LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/bin/make -npf Makefile.gbuild all" cmd || true) | C:/sources/libo-core/bin/gbuild-to-ide --ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:

After that, the LibreOffice.sln file is 353 bytes and only contains this:

Microsoft Visual Studio Solution File, Format Version 12.00
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Unit Tests|Win32 = Unit Tests|Win32
Integration tests|Win32 = Integration tests|Win32
Build|Win32 = Build|Win32
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
EndGlobalSection
EndGlobal

and there are no other recently created *.sln files in the entire source/build directory tree.

The error from make (Error 127) is not so helpful and gives me no clue to what is wrong.

Does anybody know what could be wrong? 

I would really like to be able to use the comfort of Visual Studio to browse around the source code.

Best regards,
Jesper



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

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

I tried running the command 

LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/bin/make -npf Makefile.gbuild all" cmd

which gave this output of 4359 lines:

echo "custom cmd" && ( C:/cygwin/opt/lo/bin/make -npf Makefile.gbuild all )
custom cmd
# make[1]: Entering directory 'C:/sources/libo-core'
[build DEP] LNK:Library/saxlo.dll
[build LNK] Library/saxlo.dll
S=C:/sources/libo-core && I=$S/instdir && W=$S/workdir &&  mkdir -p $W/Dep/LinkTarget/Library/ && RESPONSEFILE=C:/cygwin/tmp/gbuild.4WaPOl && PATH="C:\sources\libo-core\instdir\program;C:\sources\libo-core\instdir\program;$PATH"   $W/LinkTarget/Executable/concat-deps.exe ${RESPONSEFILE} > $W/Dep/LinkTarget/Library/saxlo.dll.d.tmp && rm -f ${RESPONSEFILE}
mv C:/sources/libo-core/workdir/Dep/LinkTarget/Library/saxlo.dll.d.tmp C:/sources/libo-core/workdir/Dep/LinkTarget/Library/saxlo.dll.d
TEMPFILE=C:/cygwin/tmp/gbuild.oMUicA &&  mv ${TEMPFILE} C:/sources/libo-core/workdir/LinkTarget/Library/saxlo.dll.objectlist

[… and lots more, ending with this: …]

[build CXX] sc/source/core/opencl/op_statistical.cxx
[build CXX] sc/source/core/opencl/op_array.cxx
[build CXX] sc/source/core/opencl/op_logical.cxx
[build CXX] sc/source/core/opencl/op_spreadsheet.cxx
[build SDI] sw/sdi/swslots
S=C:/sources/libo-core && I=$S/instdir && W=$S/workdir &&  mkdir -p $W/SdiTarget/sw/sdi/
Makefile:193: recipe for target 'cmd' failed
make: *** [cmd] Error 127


Line 193 of Makefile is the line:

echo "custom cmd" && ( $(cmd) )


Does that help in finding the cause?


2015-02-16 21:19 GMT+01:00 Jesper Hertel <[hidden email]>:
I tried running make with the --debug parameter, and that gave this output, if that is helpful:

$ /opt/lo/bin/make --debug vs2013-ide-integration
GNU Make 4.0
Built for Windows32
Copyright (C) 1988-2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
GNU Make 4.0
Built for Windows32
Copyright (C) 1988-2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Updating goal targets....
 File 'vs2013-ide-integration' does not exist.
Must remake target 'vs2013-ide-integration'.
cd C:/sources/libo-core && (LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/
bin/make -npf Makefile.gbuild all" cmd || true) | C:/sources/libo-core/bin/gbuild-to-ide -
-ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:
Successfully remade target file 'vs2013-ide-integration'.


Jesper

2015-02-16 20:40 GMT+01:00 Jesper Hertel <[hidden email]>:
Hi,

I just tried building LibreOffice for 32-bit Windows on a 64-bit Windows 7 Home Premium machine using Visual Studio 2013 Community Edition. 

I have never built LibreOffice before, and I have carefully followed the instructions from https://wiki.documentfoundation.org/Development/BuildingOnWindows and used all the recommended settings and paths. My Cygwin is 64-bit and the used Java JDK is 32-bit. 

My autogen.input for building LibreOffice is this:

--with-parallelism=2
--disable-odk
--with-junit=/cygdrive/c/sources/junit-4.10.jar
--with-ant-home=/cygdrive/c/sources/apache-ant-1.9.4
--with-jdk-home=/cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31
--enable-pch
--disable-ccache
--disable-activex
--disable-atl

and I ran the build from the Cygwin bash shell using this command:

./autogen.sh && /opt/lo/bin/make 

with current directory being

/cygdrive/c/sources/libo-core

which is the root of the tree cloned from git://gerrit.libreoffice.org/core.

As instructed, I built directly to the source tree to get Visual Studio integration.

After the first attempted builds failed, I pulled a more recent master that didn't fail on Tinkerbox, and I think the build succeeded then. There were no errors, but there were also no "Build successful" message or similar in the end. The output just ended with this:

[build SLC] sw
[build SLC] libreoffice
[build SLC] loaded modules: UnoControls accessibility accessories android animations apache-commons apple_remote avmedia basctl basebmp basegfx basic bean beanshell binaryurp boost bridges canvas chart2 clew cli_ure clucene codemaker coinmp collada2gltf comphelper configmgr connectivity cppcanvas cppu cppuhelper cppunit cpputools cui curl dbaccess desktop drawinglayer dtrans editeng embeddedobj embedserv eventattacher expat extensions external extras filter firebird forms formula fpicker framework glew glm graphite helpcompiler hsqldb hunspell hwpfilter hyphen i18nlangtag i18npool i18nutil icu idl idlc instsetoo_native iojavaunohelper jfreereport jpeg-turbo jurt jvmaccess jvmfwk l10ntools lcms2 libabw libcdr libcmis libebook libetonyek libexttextcat libfreehand libgltf liblangtag libmspub libmwaw libodfgen liborcus libpagemaker libpng librelogo libreoffice libreofficekit librevenge libvisio libwpd libwpg libwps libxml2 libxmlsec libxslt lingucomponent linguistic lotuswordpro lpsolve mdds more_fonts msc-externals mythes neon nss o3tl offapi officecfg oovbaapi ooxopencl opencollada openssl package poppler postgresql postprocess python3 pyuno qadevOOo readlicense_oo redland registry remotebridges reportbuilder reportdesign rhino ridljar rscsal salhelper sax sc scaddins sccomp scp2 scripting sd sdext setup_native sfx2 shell slideshow smoketest solenv soltools sot starmath stoc store svgio svl svtools svx sw swext sysui test testtools toolkit tools tubes ucb ucbhelper ucpp udkapi unodevtools unoidl unoil unotest unotools unoxml ure uui vbahelper vcl vigra winaccessibility wizards writerfilter writerperfect xmerge xmlhelp xmloff xmlreader xmlscript xmlsecurity zlib

But after that, it was possible to start LibreOffice Dev using C:\sources\libo-core\instdir\program\soffice.exe, so I guess the build was successful???

Then I tried to build the Visual Studio 2013 solution file using
/opt/lo/bin/make vs2013-ide-integration
with current directory being /cygdrive/c/sources/libo-core.

That gave me this entire output:

cd C:/sources/libo-core && (LC_MESSAGES=C C:/cygwin/opt/lo/bin/make cmd="C:/cygwin/opt/lo/bin/make -npf Makefile.gbuild all" cmd || true) | C:/sources/libo-core/bin/gbuild-to-ide --ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:

After that, the LibreOffice.sln file is 353 bytes and only contains this:

Microsoft Visual Studio Solution File, Format Version 12.00
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Unit Tests|Win32 = Unit Tests|Win32
Integration tests|Win32 = Integration tests|Win32
Build|Win32 = Build|Win32
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
EndGlobalSection
EndGlobal

and there are no other recently created *.sln files in the entire source/build directory tree.

The error from make (Error 127) is not so helpful and gives me no clue to what is wrong.

Does anybody know what could be wrong? 

I would really like to be able to use the comfort of Visual Studio to browse around the source code.

Best regards,
Jesper




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

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

In reply to this post by Jesper Hertel
Hi

On 2015-02-16 09:40 PM, Jesper Hertel wrote:
>
> As instructed, I built directly to the source tree to get Visual Studio integration.
>

The Visual Studio integration is, I'm afraid, largely DIY. Not many of us use it, so if it doesn't work for you, and you
can't figure it out yourself, you're out of luck :-(

However, that doesn't mean you can't use Visual Studio for debugging, it is very simple to just run VS and start a
program and debug from it, and it will load the correct source files, etc.

Regards, Noel.

Disclaimer: http://www.peralex.com/disclaimer.html


_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Tor Lillqvist-2 Tor Lillqvist-2
Reply | Threaded
Open this post in threaded view
|

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

> Not many of us use it,

True.

> However, that doesn't mean you can't use Visual Studio for debugging, it is very simple to
> just run VS and start a program and debug from it, and it will load the correct source files, etc.

In more detail, what works fine is: Start the LibreOffice you just
built (presumably with debugging information --enable-debug) by
running instdir/program/soffice.exe. Start Visual Studio, but don't
open or create any project or solution. (It makes no difference
whether you start LibreOffice or Visual Studio first.)

Then attach the soffice.bin (not soffice.exe) process in Visual
Studio. soffice.bin is the actual LibreOffice process. Then open the
source file(s) you want to debug in Visual Studio and set one or
several breakpoints. Then do whatever is needed in LibreOffice to
cause the breakpoint to be reached. Then debug.

Obviously, this way, attaching to an already running LibreOffice
process, you won't be able to debug the start-up code in LibreOffice.
But that is seldom what one would want to debug anyway.

> I would really like to be able to use the comfort of Visual Studio to
> browse around the source code

I am not sure if the Visual Studio "integration" even if it worked as
advertised would match your expectations. But I might be too
pessimistic. Maybe somebody who actually has used (or even worked on)
the integration can respond.

--tml
_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Jesper Hertel Jesper Hertel
Reply | Threaded
Open this post in threaded view
|

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows


Den 17/02/2015 07.34 skrev "Tor Lillqvist" <[hidden email]>:
>
> > Not many of us use it,
>
> True.

I know. :-)

And maybe I will have to see it as a do-it-yourself project then, as Noel suggested. I already started debugging the makefile and Python script involved. I will probably learn something new in the process. :-)

>
> > However, that doesn't mean you can't use Visual Studio for debugging, it is very simple to
> > just run VS and start a program and debug from it, and it will load the correct source files, etc.
>
> In more detail, what works fine is: Start the LibreOffice you just
> built (presumably with debugging information --enable-debug) by
> running instdir/program/soffice.exe. Start Visual Studio, but don't
> open or create any project or solution. (It makes no difference
> whether you start LibreOffice or Visual Studio first.)
>
> Then attach the soffice.bin (not soffice.exe) process in Visual
> Studio. soffice.bin is the actual LibreOffice process. Then open the
> source file(s) you want to debug in Visual Studio and set one or
> several breakpoints. Then do whatever is needed in LibreOffice to
> cause the breakpoint to be reached. Then debug.

Well, I will at least try that. Thanks for the instructions. :-)

> I am not sure if the Visual Studio "integration" even if it worked as
> advertised would match your expectations. But I might be too
> pessimistic.

I saw a video of what was possible [1] and it looked fine to me. :-) Autocomplete, IntelliSense, immediate indication of errors in the source code while you write it, instant navigation to definitions of methods etc., and stuff like that. That was what made me want to try.

[1]: https://www.youtube.com/watch?v=Xn3CtIrMpIA

> Maybe somebody who actually has used (or even worked on)
> the integration can respond.

Yes, I hoped to reach somebody who did, even though I know they are not many. But I'll just try to do it myself then.

Thanks a lot for your answers, Noel and Tor!

Jesper

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

AW: Error building Visual Studio 2013 project file for LibreOffice on Windows

Hi Jesper,

I have the same problem with the Visual Studio Solutions.

A lot of thanks too David Ostrovsky he has found a solution for that.
The solution is:

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.

I have make a small script calling "mvs": (mvs = make VS)
mvs-------------------------- start ----------------------
#!/usr/bin/bash

echo remove old files
rm -fr *.sdf *.sln *.v11* *.vcxproj* *.opensdf *.v12*

echo Generate VS Files
/opt/lo/bin/make_o -npf Makefile.gbuild all | ./bin/gbuild-to-ide --ide vs2013
mvs--------------------------end-------------------------

make_o ==> make old

And for the normal build I use "mco": (mco = make color)
mco----------------------------start----------------------------
#!/usr/bin/bash

/opt/lo/bin/make gb_COLOR=1 $1 $2 $3 $4 $5 $6 $7 $8 $9
mco-----------------------------end----------------------------


You should first generate the core in the CORE, and then you call the script for build the VS-Solution, all from the core directory


I use the VAssistx it is better as VS-IntelliSense, but it is not free
I debug with the loaded project in VS, it not a problem
When you need to debug the start phase, for that I have a solution too with VS

And last here my autogen.input
--enable-pch
--disable-ccache
--enable-dbgutil
--with-external-tar=/cygdrive/d/src/lo/externalsrc
--with-ant-home=/cygdrive/d/src/lo/apache-ant-1.9.4
--with-junit=/cygdrive/d/src/lo/junit-4.10.jar
--with-visual-studio=2013
--disable-activex
--disable-atl
--with-jpeg-turbo=0
--with-lang=de en-GB



Hope that help

Juergen

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

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

Thank you so much, Jürgen! 

I am looking forward to trying that out.


Jesper


2015-02-20 12:48 GMT+01:00 Juergen Funk Mailinglist <[hidden email]>:
Hi Jesper,

I have the same problem with the Visual Studio Solutions.

A lot of thanks too David Ostrovsky he has found a solution for that.
The solution is:

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.

I have make a small script calling "mvs": (mvs = make VS)
mvs-------------------------- start ----------------------
#!/usr/bin/bash

echo remove old files
rm -fr *.sdf *.sln *.v11* *.vcxproj* *.opensdf *.v12*

echo Generate VS Files
/opt/lo/bin/make_o -npf Makefile.gbuild all | ./bin/gbuild-to-ide --ide vs2013
mvs--------------------------end-------------------------

make_o ==> make old

And for the normal build I use "mco": (mco = make color)
mco----------------------------start----------------------------
#!/usr/bin/bash

/opt/lo/bin/make gb_COLOR=1 $1 $2 $3 $4 $5 $6 $7 $8 $9
mco-----------------------------end----------------------------


You should first generate the core in the CORE, and then you call the script for build the VS-Solution, all from the core directory


I use the VAssistx it is better as VS-IntelliSense, but it is not free
I debug with the loaded project in VS, it not a problem
When you need to debug the start phase, for that I have a solution too with VS

And last here my autogen.input
--enable-pch
--disable-ccache
--enable-dbgutil
--with-external-tar=/cygdrive/d/src/lo/externalsrc
--with-ant-home=/cygdrive/d/src/lo/apache-ant-1.9.4
--with-junit=/cygdrive/d/src/lo/junit-4.10.jar
--with-visual-studio=2013
--disable-activex
--disable-atl
--with-jpeg-turbo=0
--with-lang=de en-GB



Hope that help

Juergen



_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Ashod Nakashian-2 Ashod Nakashian-2
Reply | Threaded
Open this post in threaded view
|

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

In reply to this post by Juergen Funk Mailinglist
I haven't tried a different version of make as Juergen suggests, but I confirm that the issue has to do with the fact that make doesn't generate the invariant data that the python script excepts. Specifically, all the # lines that contain the paths and filenames are missing from the output, hence the python script's failure to generate proper project/solution files.

I know I built the latest gmake for libreoffice and I also know that I've successfully generated project/solution files at certain points in the past couple of months. I suspect make breaks due to --enable-dbgutil, but haven't verified. So using a minimal configure flags it might work.

On Fri, Feb 20, 2015 at 6:48 AM, Juergen Funk Mailinglist <[hidden email]> wrote:
Hi Jesper,

I have the same problem with the Visual Studio Solutions.

A lot of thanks too David Ostrovsky he has found a solution for that.
The solution is:

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.

I have make a small script calling "mvs": (mvs = make VS)
mvs-------------------------- start ----------------------
#!/usr/bin/bash

echo remove old files
rm -fr *.sdf *.sln *.v11* *.vcxproj* *.opensdf *.v12*

echo Generate VS Files
/opt/lo/bin/make_o -npf Makefile.gbuild all | ./bin/gbuild-to-ide --ide vs2013
mvs--------------------------end-------------------------

make_o ==> make old

And for the normal build I use "mco": (mco = make color)
mco----------------------------start----------------------------
#!/usr/bin/bash

/opt/lo/bin/make gb_COLOR=1 $1 $2 $3 $4 $5 $6 $7 $8 $9
mco-----------------------------end----------------------------


You should first generate the core in the CORE, and then you call the script for build the VS-Solution, all from the core directory


I use the VAssistx it is better as VS-IntelliSense, but it is not free
I debug with the loaded project in VS, it not a problem
When you need to debug the start phase, for that I have a solution too with VS

And last here my autogen.input
--enable-pch
--disable-ccache
--enable-dbgutil
--with-external-tar=/cygdrive/d/src/lo/externalsrc
--with-ant-home=/cygdrive/d/src/lo/apache-ant-1.9.4
--with-junit=/cygdrive/d/src/lo/junit-4.10.jar
--with-visual-studio=2013
--disable-activex
--disable-atl
--with-jpeg-turbo=0
--with-lang=de en-GB



Hope that help

Juergen

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


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

Re: Error building Visual Studio 2013 project file for LibreOffice on Windows

Ashod Nakashian-2 wrote
I haven't tried a different version of make as Juergen suggests, but I
confirm that the issue has to do with the fact that make doesn't generate
the invariant data that the python script excepts. Specifically, all the #
lines that contain the paths and filenames are missing from the output,
hence the python script's failure to generate proper project/solution files.

About a year ago, I setup my build environment with Lode and I had no issues with building a VS2013  project file. Recently I had to reset my Windows 10 install. With a clean install windows and Lode, now I'm getting the  "make[1]: *** [cmd] Error 127" when I try to make a project file.

Is Lode pulling a new version of make that's causing this error? Has anyone come up with a work-around?