World: r3wp

Well, I fear that is not true.

How so?

Diff your own releases and you will see.

Here's the diff of host-lib.h in between Win32 A107 and Linux A107:
https://gist.github.com/353ad14fedab30dddd83

libr3 on Linux and Amiga expects a hostlib vector of size 33, r3.dll 
on Win32 one of size 31.

I reported that back for A102.

There's something wrong with that diff... where did you get Linux 
A107 host-kit?

http://www.rebol.com/r3/changes.html

There's nothing wrong with that diff, it's been that way since A102. 
And it still is that way in A109.

But don't take my word for it, diff the downloads you provide on 
your site.

Well, there is a problem, because the libr3.so must be in sync.

libr3.so is in sync with the hostkit sources. It's just not in sync 
with r3.dll.

I'd say just hold off right now... I'm going to be changing the host-kit 
release mechanism very soon.

Looking forward to it ...

And once again: I'd be happy to help you with builds, automated builds 
and automated testing for R3.

There will be a host-kit release archive, then there will be the 
separate dll/so objects in a table.

The issue is that the builds are automated to a whole other level... 
beyond what you are seeing in the host-kit source.

I can only judge what I see.

Correct. You're seeing a snapshot.

And from what I see, there is not much automation.

The automation I am speaking off would automatically build and test 
for all supported platforms on each commit.

Yes, we are talking different types of automation.

That is the only automation that matters, though.

Would have saved you hours of time in the course of R3 alone.

Which one?

Huh?

I don't think so.

The automation you are talking about is classical language based. 
That's fine. We should use as much of it as we can.

But, if you grep the .h files, you'll notice that various ones are 
generated, not created by hand, and that's just the host-kit side.

The automation I am talking about is language agnostic.

The fact that the host-lib is out of sync is an interesting puzzle. 
In theory, that is impossible to have happen if a /Core is released 
along with a /Host-Kit.

I understand. You're talking about makefile automation. The build 
process is far more complex than that.

No, I am talking about automated builds.

And automated tests. The kids call it "continuous integration" these 
days.

That is a process and as such language and toolchain agnostic.

Continuous integration is really a separate dimension from automation... 
it's a set of objectives for more frequently producing test targets.

If that's what you're suggesting, I'm all for it.

Yes, that's what I am suggesting.

Automated builds, automated testing, automated release packaging.

Revision control, test suites, rapid/daily builds, easy downloading 
of results.

And whatever you want to call it, the process is simple: you have 
a single code base, version controlled. Upon every change to this 
code base, you automatically build and test on all supported platforms.

Yes, exactly. But not "rapid" or "daily" builds, automated builds.

Without human intervention. You commit a piece of code, and automagically 
7 machines pick up the changes and start building.

Continuous integration is really a separate dimension from automation.

We've been doing that since 1999.

Build automation and test automation is one integral part of modern 
CI.

carl, I have to go now... take a peek at the private messages... 
I'll pick up later.

M: ok

BTW, Jeff Kreis (at REBOL) wrote the system we used for full cross 
platform networked automated builds.

Time to get that going again for R3.