World: r3wp

If you don't post the URL, you'll simply not get the issues reported.

The host-kit can be built by any reasonable C and C++ compiler/linker.

k - I was able to build the a96 one - will give this one a go too

I'm fine with posting it.  But, I don't have the bandwidth for the 
backchannel, so we need someone else to handle that.

www.rebol.com/r3/downloads/host-kit-a100.zip

Thanks.

Any timeline for a Linux libr3.so?

also appreciate the link, Carl

Pretty easy to do, but let's take this one step first.

Do you have an integrated cross-plattform build for the host-kit?

Graham: I got the message on protocols and it's on the list.

If not, someone could write one, if you release a Linux hostkit as 
well. If you do, why not release a single cross-platform package?

Andreas, no, but only because not yet tried that.  Only minor edits 
to the makefile required to build on Linux. If you get that to work, 
then can get you the r3lib to try it. Let me know.

(That's because we don't build view yet for Linux.)

(Only Core)

Yeah, I'd really appreciate if you could send libr3.so to me. I already 
wrote an integrated build for the A96 hostkit.

What exactly do you mean "integrated build" -- you mean makefile?

A single source base which automatically builds correctly for the 
platform the build tool is invoked on.

What have you tried it on?

A96 hostkit on Linux and Win32.

Yes, it basically boils down to an adapted Makefile along with an 
auto-generated header file (or defines) for platform-specific config.

A few things on that...

The makefile is auto-generated and changes with each release. 


Also, there are big variations in make between target platforms (some 
are really horrible.) So, the makefile is kept very "dumb" to allow 
those builds.

So, we will want to get the makefile maker to do the right thing.

Second, the config controls are already part of R3, and are triggered 
by the reb-to.h file.

I used CMake, which is a cross-plattform tool that automatically 
generates "project" files for a variety of targets (such as GNU Make, 
Eclipse project files, Visual Studio project files). It works great 
on Linux, Win32, OSX and is used by several high-profile projects. 
But I'm well aware that third-party tools are most likely no-go for 
REBOL, so I'm fine with all that, and can easily look into it, as 
long as there' s at least a Linux hostkit available.

So, what header files do you find a need to generate above?

I would recommend cmake as well, seems to work well

I can only talk about A96.

What is the input to cmake?

http://203.97.234.193:8080/secure/project/ViewProject.jspa?pid=10020 
... I've added a hostkit tracker to my Jira instance.

BTW, no, I'm fine with supporting as many target formats as possible!

CMake does basically the same thing your "makefile maker" tries do 
to.

So far I've built it on about 5 different targets... but there are 
many more. For instance, we've talked about ARM, but the ARM tools 
are really crude (at least what I've got here.)

The most common ARM tooling is just GCC.

CMake Input is a "CMakeLists.txt" file, which is written in "just 
another Makefile language".

Yes, but the ARM make tool looked like 1982 the last time I tried 
it.

No idea what you tried, but you'd typically just use GNU make on 
ARM as well.

Have you tried using the makefile on BSD or OSX?

No, as there is no hostkit release for either of those.

Basically, same as Linux right now.

Can't sensibly try without e.g. a OSX dylib.

But I prodded you for weeks to build one :)

Also, problematic builds are Sun and HP Unix. But, anyway, if people 
are willing to add them, it's ok with me.

Right... I remember that now. We'll have to give it another go.

I guess sticking with the big three (+ BSD, maybe) will be sufficient 
for now.

here's the CMakeLists.txt from the OpenCV project , as an example:


https://code.ros.org/svn/opencv/tags/latest_tested_snapshot/opencv/CMakeLists.txt

In my opinion, there are bigger problems to tackle before spreading 
thin over multiple platforms makes sense.

(Eventing, for example)

Yes, of course, but if more developers get involved, the work does 
not need to be sequential.