<div dir="ltr">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.<div><br></div><div>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.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 20, 2015 at 6:48 AM, Juergen Funk Mailinglist <span dir="ltr"><<a href="mailto:Juergen.Funk_ml@cib.de" target="_blank">Juergen.Funk_ml@cib.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Jesper,<br>
<br>
I have the same problem with the Visual Studio Solutions.<br>
<br>
A lot of thanks too David Ostrovsky he has found a solution for that.<br>
The solution is:<br>
<br>
The "make version 4.0" do it wrong, I build ONLY the VS-Solution with "make version 3.82"<br>
The size is 517.746 Bytes when you have trouble to found, call me, I have forget where I downloaded.<br>
<br>
I have make a small script calling "mvs": (mvs = make VS)<br>
mvs-------------------------- start ----------------------<br>
#!/usr/bin/bash<br>
<br>
echo remove old files<br>
rm -fr *.sdf *.sln *.v11* *.vcxproj* *.opensdf *.v12*<br>
<br>
echo Generate VS Files<br>
/opt/lo/bin/make_o -npf Makefile.gbuild all | ./bin/gbuild-to-ide --ide vs2013<br>
mvs--------------------------end-------------------------<br>
<br>
make_o ==> make old<br>
<br>
And for the normal build I use "mco": (mco = make color)<br>
mco----------------------------start----------------------------<br>
#!/usr/bin/bash<br>
<br>
/opt/lo/bin/make gb_COLOR=1 $1 $2 $3 $4 $5 $6 $7 $8 $9<br>
mco-----------------------------end----------------------------<br>
<br>
<br>
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<br>
<br>
<br>
I use the VAssistx it is better as VS-IntelliSense, but it is not free<br>
I debug with the loaded project in VS, it not a problem<br>
When you need to debug the start phase, for that I have a solution too with VS<br>
<br>
And last here my autogen.input<br>
--enable-pch<br>
--disable-ccache<br>
--enable-dbgutil<br>
--with-external-tar=/cygdrive/d/src/lo/externalsrc<br>
--with-ant-home=/cygdrive/d/src/lo/apache-ant-1.9.4<br>
--with-junit=/cygdrive/d/src/lo/junit-4.10.jar<br>
--with-visual-studio=2013<br>
--disable-activex<br>
--disable-atl<br>
--with-jpeg-turbo=0<br>
--with-lang=de en-GB<br>
<br>
<br>
<br>
Hope that help<br>
<span class="HOEnZb"><font color="#888888"><br>
Juergen<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
LibreOffice mailing list<br>
<a href="mailto:LibreOffice@lists.freedesktop.org">LibreOffice@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/libreoffice" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libreoffice</a><br>
</div></div></blockquote></div><br></div>