<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><span style="font-size: 12pt;">It is very easy to install.</span><div><br></div><div><br></div><div>"We" run make-dist.py and get out a "min" install and an "all" install (per platform).</div><div>You pick one, extract it, set $PATH optionally, and you are done -- run cm3 either via $PATH or by full path.</div><div><br></div><div><br></div><div>There is some chance our binaries built on a "new" system won't run on an "old" system.</div><div>We can mitigate that by deferring some of the build to install time.</div><div>I hope to have a better story here, a more "sourcey" distribution, that is easy to install.</div><div>But the binary distributions usually work well.</div><div><br></div><div><br></div><div>Sometimes you have to edit the config files, but I have endeavored to make that not necessary.</div><div><br></div><div><br></div><div>There is another install path that prompts for path to compiler, linker, etc., even tries to figure it out. But I don't use that. I think it isn't needed.</div><div><br></div><div><br></div><div>Yes we support significantly more than x86/amd64.</div><div><br></div><div><br></div><div>We have SPARC32_SOLARIS and SPARC64_SOLARIS, that I test on the opencsw machines -- very recently even.</div><div>In the 5.8.6 timeframe, I was setup to build and test PPC_DARWIN, PPC_LINUX, SPARC32_LINUX.</div><div>Look at m3-sys/m3cc/src/buildmany.sh. All but ARM_DARWIN there i just built tonight -- the gcc-based backend.</div><div><br></div><div><br></div><div>Our portability rests on gcc, or now a C compiler, or now maybe LLVM, Posix or NT for I/O, networking, threads, etc., and X windows or Win32.</div><div>That is, while we don't run in a browser, we can run almost anywhere else, generally because other people have ported their underlying systems everywhere.</div><div><br></div><div>(Run in a browser though: LLVM w/ emcriptem backend)</div><div><br></div><div><br></div><div>The system was already very portable. I have made it easier to port.</div><div><br></div><div><br></div><div>I assume the "difficult" goals are meant to be ensure that people don't have to jump through the hoops of "install lots of extra stuff" to get it to work.</div><div><br></div><div><br></div><div>Most people will overshoot the minimal install requirements, but they will overshoot differently.</div><div>I</div><div><br></div><div> - Jay</div><br><br><div>> Date: Fri, 14 Aug 2015 06:36:29 +0000<br>> From: microcode@zoho.com<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] Build Server - Plan<br>> <br>> On Thu, Aug 13, 2015 at 01:27:54PM -0700, Darko Volaric wrote:<br>> > I'm setting up a server for building CM3 that takes a "minimalist" approach.<br>> > <br>> > It's a machine running several virtual machines, one for each platform<br>> > supported by CM3. Each VM will contain clean install of the OS plus any<br>> > external tool dependencies. It will have a minimal compiler install,<br>> > basically enough to compile itself for the host target.<br>> <br>> Doesn't CM3 support Solaris SPARC? As far as I know there is no cheap way to<br>> emulate this from Intel.<br>> <br>> > The publicly available build products will be:<br>> > <br>> > - minimal executables for bootstrap, eg the frontend and a backend<br>> > - model compiler config files<br>> > - compilation logs for bootstrap executables<br>> > - compilation logs for most modules in the github repository<br>> > - logs for certain tests<br>> <br>> This sounds like a setup for experts. Why not make a turn-key tarball<br>> available like was available (I think) before?<br>> <br>> > Packages, libraries, scripts and non-essential tools or executables will<br>> > not be built or used, the idea being that people take the minimal<br>> > bootstraps and build from there.<br>> <br>> That's fine for the 3 or 4 core guys doing all the work! For everybody else<br>> this is a big inhibitor to making CM3 generally useful to the rest of the<br>> world- unless the instructions to get a complete install are very clear and<br>> easy to follow. But it seems from watching the discussion here it is<br>> non-trivial to get CM3 installed.<br>> <br>> <br>> _______________________________________________<br>> M3devel mailing list<br>> M3devel@elegosoft.com<br>> https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel<br></div> </div></body>
</html>