Comments

Jakub Jermář

30 Mar 2013 10:25

There will be a day when we will need to run this script from inside HelenOS. Assuming we will have Python, but not a classical Unix shell, shouldn't the script be rather written in Python?

Jakub Jermář

30 Mar 2013 10:27

Btw, is the repository public? I get the following error when trying to clone it:

[jermar@gorgo software]$ git clone git@github.com:vhotspur/coastline.git
Cloning into 'coastline'...
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Vojtěch Horký

30 Mar 2013 18:27

Btw, is the repository public?

Hmm, somehow GitHub has different opinion of what is read-only... I changed the link, it should work now. Thanks for noticing.

shouldn't the script be rather written in Python?

First of all, I am not very strong with Python and the script is mostly about launching other programs, thus Unix shell was quite natural choice. But even if it would be written in Python, we would still need to have the Unix shell there because of the configure scripts. Anyway, it is just a temporary tool that makes porting efforts better reproducible. Nothing more, nothing less.

Jakub Jermář

3 Apr 2013 00:13

Ok, I managed to install zlib and libgmp. It looks like http://www.mpfr.org/mpfr-current/mpfr-3.1.1.tar.bz2 has disappeared in the meantime, preventing the build of libmpfr.

Once you have the directory structure, it is quite easy to work with the script, still I have some ideas how to improve the user experience:

How about supporting a hosted mode in which the coastline repo would be cloned directly into the HelenOS tree root and initialized by something like hsct.sh init-hosted? Switching between the coast-build and the HelenOS source tree could be then automated.

Do you think it will be once possible to support also pcc, binutils and even python builds in coastline?

Vojtěch Horký

3 Apr 2013 14:28

Ok, I managed to install zlib and libgmp. It looks like http://www.mpfr.org/mpfr-current/mpfr-3.1.1.tar.bz2 has disappeared in the meantime, preventing the build of libmpfr.

First of all, thanks for trying it. The link was fixed, you may need to remove empty file from the sources/ folder.

How about supporting a hosted mode in which the coastline repo would be cloned directly into the HelenOS tree root and initialized by something like hsct.sh init-hosted?

I am not 100% sure about cloning the repo directly into the HelenOS tree but adding an option to create the config file sounds like a good idea.

Switching between the coast-build and the HelenOS source tree could be then automated.

What you mean by switch here?

Do you think it will be once possible to support also pcc, binutils and even python builds in coastline?

Yes. I think it is a good idea to have the ported applications in a different repository and leave in the source tree only the libraries/programs created primarily for HelenOS. I am planning to try to move PCC to coastline and, maybe, eventually remove it from the HelenOS source tree. But it is too early for that. Regarding Python - that should be relatively easy: it uses my old configure helper script and actually some of the patches sent to the ML correspond (more or less) with my GCC branch.

Jakub Jermář

3 Apr 2013 17:22

What you mean by switch here?

Go to coast-build, build zlib, go to HelenOS dir, rebuild, go to coast-build, build something else, go to HelenOS dir, rebuild etc...

Jakub Jermář

3 Apr 2013 21:07

And of course, a formal description of harbour dependencies and transitive installation of these dependencies would be nice. If everything POSIX-like will be eventually moved to coastline, we could move the entire libposix there too.