• Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r4wp

[Ann-Reply] Reply to Announce group

Cyphre
9-Jan-2013
[1127]
Thanks a lot Bo! To make things easier, all donations for the R3/Droid 
port I'm wokring on are going thru Saphirion's webpage.
Robert
9-Jan-2013
[1128]
Bo, thanks a lot! That's really great.
MagnussonC
11-Jan-2013
[1129]
Good job with the prebuild site
Andreas
11-Jan-2013
[1130]
Thanks!
PeterWood
11-Jan-2013
[1131]
A very kind gift to the REBOL community.
DocKimbel
11-Jan-2013
[1132]
Nice work Andreas!
Ladislav
11-Jan-2013
[1133]
Andreas: you should let Carl know by mentioning it on the GitHub, 
I think
Andreas
11-Jan-2013
[1134]
I wrote Carl a mail to tell him about it.
DideC
11-Jan-2013
[1135]
Yes, Andreas, very nice looking site. And thanks too to Saphirion 
for the build farm.
Andreas
11-Jan-2013
[1136x2]
Build farm is 2/3 mine, 1/3 Saphirion :)
Saphirion contributes the OSX machine, for which I'm very grateful.
Endo
11-Jan-2013
[1138]
Very nice work Andreas!
Maxim
11-Jan-2013
[1139]
Andreas, good idea.


I'd only add that you should append the rebol version to the executables/archives 
(if ever), so that when we download them, they don't overwrite each 
other.  adding the version will also classify each version based 
on its platform.
Andreas
11-Jan-2013
[1140x2]
Maxim, thanks.
The version is already appended to the executable names, that's the 
-g.... suffix. For these automated builds, the Rebol version is currently 
rather meaningless, it will always be 2.101.0.


I'll think about appending a platform key to the binary names themselves.
Maxim
11-Jan-2013
[1142x2]
thanks for considering it.    :-)
at some point, the version will be incremented no?
AdrianS
11-Jan-2013
[1144]
Are you going to keep older versions?
Maxim
11-Jan-2013
[1145]
when some dramatic changes will occur, it might be necessary... for 
example, some tools might require older binaries until they are updated.
AdrianS
11-Jan-2013
[1146]
it would be good for doing triage on bugs
Maxim
11-Jan-2013
[1147]
maybe, simply adding a folder with the date of any automated builds. 
 this way we can easily backtrack any issues in time.
AdrianS
11-Jan-2013
[1148]
sorry, meant doing something like bisect of version control, not 
triage
Andreas
11-Jan-2013
[1149]
binaries are not deleted, so you can still download them, if you 
have the url. i'll probably add an archive page later on.
AdrianS
11-Jan-2013
[1150]
What about the points I asked about in the community group? Not worth 
it, you think?
Andreas
11-Jan-2013
[1151x3]
ah, sorry, forgot about those questions :)
compiler switches: i'm currently building from the mainline sources 
without any custom modifications.
so typically a build is just three steps:
- fetching an r3-make
- make make
- make clean prep
AdrianS
11-Jan-2013
[1154]
well, some build details might be nice - for example under Windows 
which toolchain was used - these details might be important if/when 
people start comparing performance among builds gotten here and elsewhere
Andreas
11-Jan-2013
[1155x2]
toolchain is mentioned on the downloads page.
win7, gcc 4.6.2, r3 2.100.111.3.1 for bootstrapping
AdrianS
11-Jan-2013
[1157]
I'm blind
Andreas
11-Jan-2013
[1158x3]
if you need/want more detail, just ask away
debug builds: maybe. i'd like to get this added to the mainline sources 
first. once that's done, i'm still not so sure if they really are 
that useful at the moment, as I think they won't help much without 
a build environment set up.
but then, why not :)
AdrianS
11-Jan-2013
[1161x3]
if you provided symbols, you could have useful output even with something 
like process explorer
and maybe a link to how to use the symbols with process explorer 
- this would allow relatively non-technical people report readable 
stack traces on a hang, for example
maybe point to this, if you add symbols:


http://superuser.com/questions/462969/how-can-i-view-the-active-threads-of-a-running-program
Andreas
11-Jan-2013
[1164]
well, with the basic build farm in place and the website launched, 
i'll maybe get to some more build process revisions (including debug 
builds) soon.
GrahamC
11-Jan-2013
[1165x2]
Nice .. are you adopting fork's logo for the open source rebol now 
:)  ?
Some sites like to add md5 checksums to their downloads pages
Gregg
11-Jan-2013
[1167]
Thanks, to Andreas and the Saphirion team!
Bo
11-Jan-2013
[1168]
I'm good with Fork's logo.  If the community agrees on a different 
one in the future, it could be changed.  Some projects, like Cobian 
Backup, have a different logo for each major release. :-O
sqlab
12-Jan-2013
[1169]
speed?/no-io
[956 560 23 0] 
on Samsung Note II
Andreas
12-Jan-2013
[1170]
Graham, did you ever check the md5sums?
sqlab
12-Jan-2013
[1171]
without power saving
[1489 811 33 0]
Ladislav
12-Jan-2013
[1172]
aha, I was surprised by your first result, sqlab
sqlab
12-Jan-2013
[1173]
I too.)
GrahamC
12-Jan-2013
[1174]
Andreas, yes for ISO images :)
Gerard
12-Jan-2013
[1175]
Thanks Andreas, Cyphre, Robert and all the others actively implied 
in R3 dev, the ongoing progress and all the tools you shared and 
have committed online. The R3Droid chat works well under my Android 
3.2 (Samsung Galaxy Tab 10.1). and the chat also runs fine under 
my Win7 Toshiba -  from the binaries set online at http://www.rebolsource.net
GrahamC
14-Jan-2013
[1176]
Kaj, where exactly is the window32 binary in http://archives.esperconsultancy.nl/Red-test/dir?ci=tip
 ?


Every click on a .exe takes me to more and more html pages.  Most 
confusing.