AltME: R3 Building and Porting


@Cyphre thx!

GregP: try to compile all the cpp files and do the final linking with g++ instead of gcc (the next update on github will have the makefile improved)
Thanks a lot Cyphre, I only changed gcc into g++ to link the r3-view-host and r3-view and all compile!
My only issue now is this:
>> demo
Fetching demo...
Script: "Untitled" Version: none Date: none
Fetching GUI...
** Script error: / does not allow none! for its value2 argument
** Where: do resize-panel actor all foreach do-actor either -apply- apply case v
iew catch either either -apply- do try demo
** Near: do bind bind/copy [
    size: viewport-box/bottom-right
but I'm happy I can start playing with it anyway!

GregP: the error is fired because your compiled r3-view.exe contains more recent changes which are not reflected by the current public r3-gui build on our servers. We need to have the r3-gui build to be compatible with our current experimental binary builds. (ie. if you download our latest binary release it should always work with the latest r3-gui release)
So you are in a bit odd state now. To quickly fix that you can download the r3-gui from (same link is used in the DEMO or LOAD-GUI commands) and replace all "unit-size" string occurences to "log-size". Then you can use the r3-gui with your custom saphir build.
Otherwise we'll be soon updating our build/releases/repositories with new versions (quite a lot things happened from the last public updates) so the multiple codebases will get in sync very soon.
Change done on r3-gui.r3: it works now :)

is the community version always up to date with saphirion changes wrt core stuff?
I should have said... is the community version  **currently**  up to date with latest changes from saphirion and atronix?
I doubt it. Carl does not accept PRs, there is 37 PRs in the queue, dunno who can eventually accept them?
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.
(didn't see 'wrt core stuff')  Well, mostly up to date I guess.  There are some bug fixes

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

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:
A pre-built 64-bit Linux binary is also available under the "experimental" section on rebolsource:
If you need GUI support as well, go with Atronix' version:
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  would help
something like a symlink from  r3-g25033f8  to r3-latest  
(asuming the -g25033f8 part changes and becomes unavailable after a while)

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.

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?
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.
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.

Last message posted 90 weeks ago.