Re: Unable to Build Mono
Katelyn Gadd via Mono-devel-list <[email protected]> Thu, 1 Feb 2018 21:03:37 +0000
| Newsgroups | gmane.comp.gnome.mono.devel |
|---|---|
| Message-ID | <MWHPR21MB078339A3EE6D30F6A7240F4589FA0@MWHPR21MB0783.namprd21.prod.outlook.com> |
--===============0327945590430945565==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_MWHPR21MB078339A3EE6D30F6A7240F4589FA0MWHPR21MB0783namp_"
--_000_MWHPR21MB078339A3EE6D30F6A7240F4589FA0MWHPR21MB0783namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hi Vishnu,
Can you provide the stdout from those failed build commands? If you go to t=
he Output tab in VS2017 and select 'show output from: build' the stdout wil=
l be near where the failed build step is.
If you've already built mono successfully using Cygwin, my guess is that mo=
no is not being located to run those commands (due to not being in PATH) bu=
t I'm surprised that the exit code is different between culevel and Apigen.
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 - but that shouldn't be necessary if you have a mono.exe.
-kg
--_000_MWHPR21MB078339A3EE6D30F6A7240F4589FA0MWHPR21MB0783namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
#800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Calibri" size=3D"2"><span style=3D"font-size:11pt;">
<div>Hi Vishnu,</div>
<div> </div>
<div>Can you provide the stdout from those failed build commands? If you go=
to the Output tab in VS2017 and select ‘show output from: build̵=
7; the stdout will be near where the failed build step is.</div>
<div> </div>
<div>If you’ve 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’m surprised that the exit code is different between cu=
level and Apigen.</div>
<div> </div>
<div>Another option is to change the project settings for Apigen so that it=
builds in a .net framework compatible way, and change the build steps to r=
un it directly – but that shouldn’t be necessary if you have a =
mono.exe.</div>
<div> </div>
<div>-kg</div>
<div><font face=3D"Times New Roman"> </font></div>
</span></font>
</body>
</html>
--_000_MWHPR21MB078339A3EE6D30F6A7240F4589FA0MWHPR21MB0783namp_--
--===============0327945590430945565==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTW9uby1kZXZl
bC1saXN0IG1haWxpbmcgbGlzdApNb25vLWRldmVsLWxpc3RAbGlzdHMuZG90Lm5ldApodHRwOi8v
bGlzdHMuZG90Lm5ldC9tYWlsbWFuL2xpc3RpbmZvL21vbm8tZGV2ZWwtbGlzdAo=
--===============0327945590430945565==--