Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[slacka]

Hi Bjoern, 
Should this be working with a vanilla LODE install? With the master I'm
getting:

 $  ../../opt/bin/make vs2013-ide-integration
cd C:/cygwin/home/luke/lode/dev/core && (LC_MESSAGES=C
C:/cygwin/home/luke/lode/opt/bin/make
cmd="C:/cygwin/home/luke/lode/opt/bin/make -npf Makefile.gbuild all" cmd ||
true) | C:/cygwin/home/luke/lode/dev/core/bin/gbuild-to-ide --ide vs2013
make[1]: *** [cmd] Error 127
Solution LibreOffice:
Successfully created the project files.

Has anyone else got this working yet with LODE + vs2013? Any ideas what I
might be doing wrong? Do I need to do a fresh LODE install? 



--
View this message in context: 
http://nabble.documentfoundation.org/Fresh-install-of-Win-10-LODE-vs2013-ide-integration-Error-127-tp4195655p4197131.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[Miklos Vajna]

Hi Bjoern,

On Thu, Oct 13, 2016 at 11:25:23AM +0200, Bjoern Michaelsen 
 wrote:
> Half of this, the "export from gbuild" part, is done now:
> 
>  
> https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=f2061f85bf4d3d005668c3192589f0d242a49a36
> 
> It should be rather trivial to read that from gbuildtoide like the Pythontest
> does. If anyone wants to other fun stuff with it, feel free. Now that the base
> is there, extending this should be trvial.

As far as I understand, the 3 most used gbuild objects that contain c++
files are Library, Executable and CppunitTest. If I see correctly, the
$ide-ide-integration target takes care of Library and Executable
(ignoring CppunitTest); while this newer json export even ignores
Executables.

Would it be possible to add Executables and CppunitTests for this newer
json export? I've tried to look at this, but I didn't get far, possible
due to my weak make-fu. ;-)

(The type inspection provided by vim-ide-integration is really helpful
sometimes, and it hurts a bit that it's not available when working on
unit tests, especially when I spend half of my time there. :-) )

Thanks,

Miklos


signature.asc
Description: Digital signature
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[Bjoern Michaelsen]

Hi,

On Tue, Oct 04, 2016 at 11:26:05AM +0200, Bjoern Michaelsen wrote:
> The main trouble with all these IDE integrations seems that the output of 
> "make
> -np" on which it depends is not as stable between versions of make as
> originally expected by that naive guy who did the initial implementation. Thus
> the parser of that is both more fragile and more complex as it should be by 
> now.
> 
> I have a half-finished patch that will make make write out how it intends to
> build stuff in small (json) text files. Parsing _that_ should be really 
> trivial
> and not fragile. Also it might make possible creating:
> 
> 1/ the possiblity of creating a IDE integration without a full build
> 2/ the possiblity to create MS Build solutions for some (non-special) targets,
>thus building like MSVS would.

Half of this, the "export from gbuild" part, is done now:

 
https://gerrit.libreoffice.org/gitweb?p=core.git;a=commitdiff;h=f2061f85bf4d3d005668c3192589f0d242a49a36

It should be rather trivial to read that from gbuildtoide like the Pythontest
does. If anyone wants to other fun stuff with it, feel free. Now that the base
is there, extending this should be trvial.

Best,

Bjoern
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[Bjoern Michaelsen]

Hi,

On Tue, Oct 04, 2016 at 07:46:05AM +0200, Jan Iversen wrote:
> I use the gbuild-to-ide script regular, without problems. BUT it has severe
> limitations, it will not (and has never) made a visual studio project that
> you can actually build.
> [...]
> There is a ongoing project to enhance the script, and patches are welcome

The main trouble with all these IDE integrations seems that the output of "make
-np" on which it depends is not as stable between versions of make as
originally expected by that naive guy who did the initial implementation. Thus
the parser of that is both more fragile and more complex as it should be by now.

I have a half-finished patch that will make make write out how it intends to
build stuff in small (json) text files. Parsing _that_ should be really trivial
and not fragile. Also it might make possible creating:

1/ the possiblity of creating a IDE integration without a full build
2/ the possiblity to create MS Build solutions for some (non-special) targets,
   thus building like MSVS would.

However, for the most part, I dont think 2/ is a good idea anyway as:

a/ It would be an addition scenario to support, which is a pain
b/ we arent getting rid of needing cygwin with this anyway, so why bother?
c/ the hard part is in all the special casing and nasty custom logic, which is
   e.g. in scp2/ still -- not building a general C++ library.

So as long as scp2/ is still around, we shouldnt venture into 2/: As usual with
gbuild, the hard part is not building the new stuff, but cleaning up the old.

Best,

Bjoern
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[Jan Iversen]

I use the gbuild-to-ide script regular, without problems. BUT it has severe 
limitations, it will not (and has never) made a visual studio project that you 
can actually build.

This script (make vs2013-ide-integration) and LODE are 2 cups of coffee, that 
has nothing to do with each other. LODE is primarily made to support the 
buildbots, and then got popular as an easy way to install LO development.

The main problem with the visual integration is that you need a successful 
build first, and then you can run the script. 

There is a ongoing project to enhance the script, and patches are welcome

rgds
jan I.


> On 03 Oct 2016, at 21:50, Luke Benes  wrote:
> 
> This issue has come up before here:
> http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-project-file-for-LibreOffice-on-Windows-td4140307.html#a4140315
> 
> and more recently here:
> http://nabble.documentfoundation.org/Recommended-build-instructions-td4193014.html#a4193568
> 
> With no clear resolution.  
> 
> Over a years ago, I know that a LODE install could successfully generate VS 
> files. Since then I reinstalled Win 10 and now get the  "make[1]: *** [cmd] 
> Error 127" when I try to run vs2013-ide-integration.  Frustrated by not being 
> able to use the IDE, today I tried a fresh install of Win 10, VS 2013 and 
> LODE on a VM.  And again get:
> 
> $ C:/cygwin/home/luke/lode/opt/bin/make vs2013-ide-integration
> cd C:/cygwin/home/luke/lode/dev/core && (LC_MESSAGES=C 
> C:/cygwin/home/luke/lode/opt/bin/make 
> cmd="C:/cygwin/home/luke/lode/opt/bin/make -npf Makefile.gbuild all" cmd || 
> true) | C:/cygwin/home/luke/lode/dev/core/bin/gbuild-to-ide --ide vs2013
> make[1]: *** [cmd] Error 127
> Solution LibreOffice:
> Successfully created the project files.
> 
> 
> Has anyone other than Ashod been able to get the IDE integration recently 
> working recently?  What might be different about my environment that's 
> causing it to fail for me?
> 
> One suggestion was to keep trying several times. Today, I tried over 6 times 
> with my clean install before giving up.
> 
> The other suggestion was to use an old version of make. Could someone please 
> share the version of make that works for them on Google Drive, Dropbox, or 
> OneDrive?
> ___
> LibreOffice mailing list
> LibreOffice@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/libreoffice

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[slacka]

Yes, I had a successful build with LODE's default
autogen.input="--enable-debug". After it finished, I ran
'./instdir/program/soffice.exe' to make sure everything was actually
working. It seemed fine. So I tried several runs of
'C:/cygwin/home/luke/lode/opt/bin/make vs2013-ide-integration'. I also tried
rebooting my VM and removing the 'LibreOffice.sln' file.

This is on the same computer that ide integration used to work every time.
Could it be related to the switch from Win 7 to Win 10? Or is it more likely
that LODE pulls a different version of make (or some other file) now than it
did when ide integration was working?




--
View this message in context: 
http://nabble.documentfoundation.org/Fresh-install-of-Win-10-LODE-vs2013-ide-integration-Error-127-tp4195655p4195672.html
Sent from the Dev mailing list archive at Nabble.com.
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: Fresh install of Win 10 + LODE + vs2013-ide-integration = Error 127

[Markus Mohrhard]

Hey Luke,

On Mon, Oct 3, 2016 at 9:50 PM, Luke Benes  wrote:

> This issue has come up before here:
> http://nabble.documentfoundation.org/Error-building-Visual-Studio-2013-
> project-file-for-LibreOffice-on-Windows-td4140307.html#a4140315
>
> and more recently here:
> http://nabble.documentfoundation.org/Recommended-build-
> instructions-td4193014.html#a4193568
>
> With no clear resolution.
>
> Over a years ago, I know that a LODE install could successfully generate
> VS files. Since then I reinstalled Win 10 and now get the  "make[1]: ***
> [cmd] Error 127" when I try to run vs2013-ide-integration.  Frustrated by
> not being able to use the IDE, today I tried a fresh install of Win 10, VS
> 2013 and LODE on a VM.  And again get:
>
> $ C:/cygwin/home/luke/lode/opt/bin/make vs2013-ide-integration
> cd C:/cygwin/home/luke/lode/dev/core && (LC_MESSAGES=C
> C:/cygwin/home/luke/lode/opt/bin/make 
> cmd="C:/cygwin/home/luke/lode/opt/bin/make
> -npf Makefile.gbuild all" cmd || true) | 
> C:/cygwin/home/luke/lode/dev/core/bin/gbuild-to-ide
> --ide vs2013
> make[1]: *** [cmd] Error 127
> Solution LibreOffice:
> Successfully created the project files.
>
>
> Has anyone other than Ashod been able to get the IDE integration recently
> working recently?  What might be different about my environment that's
> causing it to fail for me?
>
> One suggestion was to keep trying several times. Today, I tried over 6
> times with my clean install before giving up.
>
> The other suggestion was to use an old version of make. Could someone
> please share the version of make that works for them on Google Drive,
> Dropbox, or OneDrive?
>


Did you do a build before calling make vs2013-ide-integration?

Regards,
Markus
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice