[M3devel] Build Server - Plan

[Darko Volaric]

Just like there are different views on how Linux should be set up and thus
different distributions, there are different views on how CM3 should be
setup or installed, or at least I have a different view.

I definitely believe in the "effortlessly and mindlessly" thing, and I want
to take it further than the current installer. In particular I want to
reduce the external, internal and environmental dependencies so that you
can build anything, anywhere with just the minimal set of executables and a
standard set of tools. Others want a more elaborate setup which gives them
more flexibility; that can also be derived from that same minimal set.



On Sun, Aug 16, 2015 at 12:27 AM, <microcode at zoho.com> wrote:

> On Fri, Aug 14, 2015 at 09:22:08AM -0700, Darko Volaric wrote:
> > The solution for SPARC might be to create a cross-compiler. That's not
> > ideal but would be useful for verifying that things compile for the
> > platform at least, short of having the right hardware.
>
> You should have access to opencsw as Jay mentioned. If not, I can offer
> machine time but I can't keep the machine running all the time. Hopefully
> the current setup (opencsw) is still viable.
>
> > I disagree with your "only for experts" assessment. The point of this
> > server is that you don't have to compiler the compiler and a backend just
> > to get the latest (or even a properly working) compiler. That's the very
> > "expert" work I'm trying to automate.
>
> That is good to hear because from your list of deliverables it seemed to me
> there would still be a lot of tinkering to get a complete install. If you
> are scripting that and it can be built effortlessly and mindlessly from the
> deliverables then good. I think it would be ideal and very nice if people
> could download a turnkey tarball ready to run on their platform, or source
> code ready to build and an installer script that installs the final
> product. Jay mentioned autotools and they are usually far from optimal on
> Solaris because of autotools reliance on so much gnu stuff that is not
> always necessarily present on Solaris but that is the general idea- to be
> able to configure && make && make install with all the standard stuff
> happening like everything being installed in /usr/local/bin|lib|share and
> so
> forth.
>
> > What this system spits out is everything you need to compile anything you
> > want - a complete and working compiler. Not everyone wants or needs to
> use
> > all the packages. If you do, you can. Here are the instructions for doing
> > that: "cd <source dir>; cm3 <options>"
>
> It was probably just my unfamiliarity with the build setup and terms. I'm
> sorry if I wasted anybody's time with this diversion. I have been following
> the mailing list and it looks like Jay and Rodney are mostly discussing
> things with a very small number of regulars. Coming from the outside as I
> do
> I think anybody new is going to have similar questions/misunderstandings of
> how cm3 is built and installed, etc.
>
> > I'll be opening up the server to anyone who wants to do something
> > different. If someone wants to produce tarballs they can setup their own
> > VMs and they will get built too.
>
> Hopefully this can be integrated with what you already have running on
> opencsw.
>
> Thank you.
>
>
> _______________________________________________
> M3devel mailing list
> M3devel at elegosoft.com
> https://mail.elegosoft.com/cgi-bin/mailman/listinfo/m3devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20150816/38ce32d1/attachment-0002.html>