Re: Unable to Build Mono
Vishnu Kalapur <[email protected]> Sun, 4 Feb 2018 21:50:13 +0000
| Newsgroups | gmane.comp.gnome.mono.devel |
|---|---|
| Message-ID | <VI1P189MB03684528FAF19A8B74DA327EA8FF0@VI1P189MB0368.EURP189.PROD.OUTLOOK.COM> |
--===============0945494350715159971== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_VI1P189MB03684528FAF19A8B74DA327EA8FF0VI1P189MB0368EURP_" --_000_VI1P189MB03684528FAF19A8B74DA327EA8FF0VI1P189MB0368EURP_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, Once again thank you for the help. I was successful I building it but, only= after changing the solution properties such that those projects do not bui= ld. As of now, it is fine for me if those projects are not built. -Vishnu Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=3D550986> for Window= s 10 From: Katelyn Gadd<mailto:[email protected]> Sent: Friday, February 2, 2018 3:28 AM To: Vishnu Kalapur<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: RE: [Mono-dev] Unable to Build Mono I=92m not certain what could be wrong with the apigen build step =96 there = is no error output =96 but the culevel failures are because culevel.exe was= not built. You should check to see whether it isn=92t being compiled for s= ome reason. It should be in the .sln file for all the assemblies. -kg From: Vishnu Kalapur [mailto:[email protected]] Sent: Thursday, February 1, 2018 17:53 To: Katelyn Gadd <[email protected]> Cc: [email protected] Subject: RE: [Mono-dev] Unable to Build Mono Hi Katelyn, Thank you for the help. I have attached the stdout from the failed build co= mmands in the text file. I have already built the mono using cygwin and add= ed the mono in path as well. Regards, Vishnu Sent from Mail<https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3= A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3D550986&data=3D02%7C01%7CKate= lyn.Gadd%40microsoft.com%7Ce3c018adcab645b269da08d569dfbad4%7Cee3303d7fb734= b0c8589bcd847f1c277%7C1%7C0%7C636531331992208806&sdata=3D14kVN1nJYrd5yIS%2F= A5dGK%2Bby9QCcUYov6V%2FS3fBYreg%3D&reserved=3D0> for Windows 10 From: Katelyn Gadd<mailto:[email protected]> Sent: Thursday, February 1, 2018 10:03 PM To: [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]> Subject: RE: [Mono-dev] Unable to Build Mono Hi Vishnu, Can you provide the stdout from those failed build commands? If you go to t= he Output tab in VS2017 and select =91show output from: build=92 the stdout= will be near where the failed build step is. If you=92ve already built mono successfully using Cygwin, my guess is that = mono is not being located to run those commands (due to not being in PATH) = but I=92m surprised that the exit code is different between culevel and Api= gen. Another option is to change the project settings for Apigen so that it buil= ds in a .net framework compatible way, and change the build steps to run it= directly =96 but that shouldn=92t be necessary if you have a mono.exe. -kg --_000_VI1P189MB03684528FAF19A8B74DA327EA8FF0VI1P189MB0368EURP_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc= hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of= fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1= 252"> <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} --></style> </head> <body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72"> <div class=3D"WordSection1"> <p class=3D"MsoNormal">Hi,</p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Once again thank you for the help. I was successful = I building it but, only after changing the solution properties such that th= ose projects do not build. As of now, it is fine for me if those projects a= re not built.</p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">-Vishnu</p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Sent from <a href=3D"https://go.microsoft.com/fwlink= /?LinkId=3D550986"> Mail</a> for Windows 10</p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div style=3D"mso-element:para-border-div;border:none;border-top:solid #E1E= 1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <p class=3D"MsoNormal" style=3D"border:none;padding:0in"><b>From: </b><a hr= ef=3D"mailto:[email protected]">Katelyn Gadd</a><br> <b>Sent: </b>Friday, February 2, 2018 3:28 AM<br> <b>To: </b><a href=3D"mailto:[email protected]">Vishnu Kalapur</a><br> <b>Cc: </b><a href=3D"mailto:[email protected]">mono-devel-list= @lists.dot.net</a><br> <b>Subject: </b>RE: [Mono-dev] Unable to Build Mono</p> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">I=92m not certain what could be wrong with the apige= n build step =96 there is no error output =96 but the culevel failures are = because culevel.exe was not built. You should check to see whether it isn= =92t being compiled for some reason. It should be in the .sln file for all the assemblies.<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">-kg<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b>From:</b> Vishnu Kalapur [mailto:vishnuk.2410@gma= il.com] <br> <b>Sent:</b> Thursday, February 1, 2018 17:53<br> <b>To:</b> Katelyn Gadd <[email protected]><br> <b>Cc:</b> [email protected]<br> <b>Subject:</b> RE: [Mono-dev] Unable to Build Mono<o:p></o:p></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Hi Katelyn,<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Thank you for the help. I have attached the stdout f= rom the failed build commands in the text file. I have already built the mo= no using cygwin and added the mono in path as well.<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Regards,<o:p></o:p></p> <p class=3D"MsoNormal">Vishnu<o:p></o:p></p> <p class=3D"MsoNormal">Sent from <a href=3D"https://na01.safelinks.protecti= on.outlook.com/?url=3Dhttps%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3FLinkId%3= D550986&data=3D02%7C01%7CKatelyn.Gadd%40microsoft.com%7Ce3c018adcab645b= 269da08d569dfbad4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531331992= 208806&sdata=3D14kVN1nJYrd5yIS%2FA5dGK%2Bby9QCcUYov6V%2FS3fBYreg%3D&= ;reserved=3D0"> Mail</a> for Windows 10<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in = 0in 0in"> <p class=3D"MsoNormal"><b>From: </b><a href=3D"mailto:Katelyn.Gadd@microsof= t.com">Katelyn Gadd</a><br> <b>Sent: </b>Thursday, February 1, 2018 10:03 PM<br> <b>To: </b><a href=3D"mailto:[email protected]">[email protected]= </a><br> <b>Cc: </b><a href=3D"mailto:[email protected]">mono-devel-list= @lists.dot.net</a><br> <b>Subject: </b>RE: [Mono-dev] Unable to Build Mono<o:p></o:p></p> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Hi Vishnu,<o:p></o:p></p> <div> <p class=3D"MsoNormal"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal">Can you provide the stdout from those failed build c= ommands? If you go to the Output tab in VS2017 and select =91show output fr= om: build=92 the stdout will be near where the failed build step is.<o:p></= o:p></p> </div> <div> <p class=3D"MsoNormal"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal">If you=92ve already built mono successfully using Cy= gwin, my guess is that mono is not being located to run those commands (due= to not being in PATH) but I=92m surprised that the exit code is different = between culevel and Apigen.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal">Another option is to change the project settings for= Apigen so that it builds in a .net framework compatible way, and change th= e build steps to run it directly =96 but that shouldn=92t be necessary if y= ou have a mono.exe.<o:p></o:p></p> </div> <div> <p class=3D"MsoNormal"> <o:p></o:p></p> </div> <div> <p class=3D"MsoNormal">-kg<o:p></o:p></p> </div> <p class=3D"MsoNormal"><span style=3D"font-family:"Times New Roman&quo= t;,serif"> </span><o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_VI1P189MB03684528FAF19A8B74DA327EA8FF0VI1P189MB0368EURP_-- --===============0945494350715159971== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTW9uby1kZXZl bC1saXN0IG1haWxpbmcgbGlzdApNb25vLWRldmVsLWxpc3RAbGlzdHMuZG90Lm5ldApodHRwOi8v bGlzdHMuZG90Lm5ldC9tYWlsbWFuL2xpc3RpbmZvL21vbm8tZGV2ZWwtbGlzdAo= --===============0945494350715159971==--