AltME: R3 Building and Porting

Messages

Maxim
is the community version always up to date with saphirion changes wrt core stuff?
Maxim
I should have said... is the community version  **currently**  up to date with latest changes from saphirion and atronix?
Pekr
I doubt it. Carl does not accept PRs, there is 37 PRs in the queue, dunno who can eventually accept them?
Josh
No, it's not up to date.  There are some diffferences in structure between the rebol repo and the other two in some places with the addition of the GUI code.
Josh
(didn't see 'wrt core stuff')  Well, mostly up to date I guess.  There are some bug fixes

Tomc
Q: Which is the most appropiate R3 GitHub repo for 64b Redhat, Debian & derivatives these days?

Andreas
Depends on if you need GUI.
If you don't need GUI support, I'd suggest going with the "community" repository. Which at the moment is basically mainline (i.e. the official codebase) + 64-bit support:
https://github.com/rebolsource/r3
A pre-built 64-bit Linux binary is also available under the "experimental" section on rebolsource:
http://www.rebolsource.net/
If you need GUI support as well, go with Atronix' version:
http://atronixengineering.com/downloads.html
Tomc
core is fine for now.
Goal is to have an established automated process to build an arbitrary version of rebolin a Docker container.
(which only suppotrs recent 64b kernels)
A fixed link to the current 64b linux binary at www.rebolsource.net  would help
something like a symlink from  r3-g25033f8  to r3-latest  
(asuming the -g25033f8 part changes and becomes unavailable after a while)

GrahamC
I think it would be nice to have a link that is easy to type as usually you have to use wget to download rebol.

GregP
I had about the same question as Maxim regarding keeping R3 source in sync between repositories. Carl open sourced R3, Saphirion brought the UI and other improvements, Atronix works on Linux. and I just wish we could consolidate all those contributions. Anyone has an insight on this?
Andreas
Needs one or more people dedicated to doing the consolidation.
At least most of the stuff is now out in the open, so anyone technically able and willing to do it, _can_ do it. But I know that doesn't help those who can't do it on their own and are (rightly) frustrated by the perceived fragmentation.
However, note that there is quite a bit of consolidation going on. Many contributions are pending as pull requests against the "mainline" repostiroy. And both Atronix and Saphirion have integrated most of the contributions into their repositories.
GregP
It is great it is now open sourced and I think it also takes time for a community to build and organize around. For example when Blender went open source it took times to get some/enough people involved. My concern about fragmentation is mostly about getting the same behavior on all plateforms.
I agree things are on a good track though.
Andreas
> My concern about fragmentation is mostly about
> getting the same behavior on all plateforms.
A concern I can very much understand and sympathise with. Ultimately, I think this needs one or more "champions" for each platform who are willing to actively involve themselves.

GregP
Is there any existing documentation around R3 implementation that would help any beginner to jump in?
Also, what's your opinion on using SDL2.0 as a R3 host ?

Kaj
SDL 2 would be a good backend to add

GregP
It would be a good backend but at the same time I wonder if it is not too much. SDL2 handles video, events, files, timer, keybaord, mouse, simple drawing, ... and R3 does many of this already. Mostly the compositor is what we miss.
Cyphre
IIRC Robert had some interest to use SDL2 as replacement of some of the host parts. But I think this is not small project. GregP, you have good point about the SDL based compositor. That could be interesting to try, but IMO it wouldn't improve the 2d vector graphics cpu performance it that's what you are after. Also I haven't researched if the SDL is modular enough so you can use only specific parts of the framework to have small footprint.

Last message posted 269 weeks ago.