Hi!
i like to say, the best thing for newbies or people who just want to quickly
play around is
to create a vmware (or virtualbox) image of the buildsystem and have a
bittorrent tracker to download it.
the only downside is the download size, but in this day and age thats hardly an
issue anymore.
the upsides are very clear.
1 click on the torrent, and after download startup the vmware and you are ready
to go.
no packages to install, no system to setup.
inside the vmware you can update the source with git, and stay uptodate.
cheers,
Zoff.
Klaus Kurzmann wrote:
Am Dienstag, 22. Februar 2011, 09:24:30 schrieb Christ van Willegen:
On Tue, Feb 22, 2011 at 8:32 AM, Ivan Nedrehagen<[email protected]>
wrote:
På Mon, 21 Feb 2011 09:42:07 +0100, skrev Christ van Willegen
<[email protected]>:
On Sun, Feb 20, 2011 at 9:34 PM, Ben Thompson<[email protected]>
wrote:
It would seem that manpower is the big problem.
Very true...
Unfortunately, I've been struggling for _months_ to get a stable,
working, build system for SHR...
I couldn't agree more. Many times I have decided to contribute. But it
has always ended with me having problems with the build. When it dawns
on me that I have spent more hours fiddling with the build system than
looking at the code, I get discouraged.
/me nods
This Thursday afternoon (CET), and probably this Friday (I'll check
back most of the day...) I'll be on irc, and perhaps tonight, so if
there's anyone willing to help me on board, I'd be very glad to be
able to help.
My experiences in FR programming so far have been minimal, but I can
read and write C/C++. So, perhaps I can go bug-chasing somewhere...
Christ van Willegen
We, or more specifically Martin, is working on integrating his chroot build
environment into our Makefile. That will at least eliminate all buildhost
related problems.
Hopefully this will help a lot in making it easier to build SHR :-)
_______________________________________________
Shr-devel mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-devel
