World: r3wp

Why those restrictions, Andreas? Core is a statically linked host 
kit.

Which restrictions?

Yes, but we can't reproduce Core from the hostkit.

I worked on the amiga python port and we provide a libpython.so which 
is what apps like Blender then utilize for embedding python

I imagine rebol will be similar

Yeah, but Python is open source :) Carl is _very_ picky about libr3.

that is what is to be expected.

(reply was for ssolie)

thanks Maxim

just thinking out loud a bit while browsing the host-kit here..

The primary reason there's no OSX hostkit is that Carl has not yet 
managed to generate a libr3 to his satisfaction :)

he says he can't generate a .so on OSX that doesn't export all symbols

strange.. I would think you just disable the option in the linker... 
--export-all-symbols or something?

Yeah, which is precisely what an .a does as well ("exporting all 
symbols", that is) :)

gcc doesn't export all symbols by default but maybe apple made some 
changes

Yeah, I sent Carl a complete example of how to achieve what he wants 
on OSX. But up until today he didn't get around to look into it.

What toolchain is used on Amiga?

gcc

+ binutils?

yes

What binary format is used?

ELF?

yes, the good old elf

Cool.

should be pretty easy I figure

Should be easy to get going then, yes.

What version of GCC do you have available?

from memory.. 4.0.3 is the current baseline

I really just think that maintaining several repos is currently to 
much work since it changes sooo oftern.  once the hostkit stabilizes 
a bit (within two or three releases is my guess) he should get around 
to concentrating on getting other distros their .so  


The amiga port was probably a good exercise in making the core lib 
even more cpu/platform agnostic.

You can't reproduce Core from the host kit? I understand that you 
can't make official binaries, but there shouldn't be anything stopping 
you from creating a single program that does everything Core does 
from the host kit once the host kit is out of alpha.

Well, there is. You can't statically link dynamic libraries.

The restrictions you are talking about are temporary. Just because 
static libraries aren't provided in this experimental release doesn't 
mean they won't be in the final release.

I'm just stating the facts.

I imagine one idea would be to provide a single executable which 
contains r3 core and the app to keep things as simple as possible 
for some devices.

The main reason you are unlikely to get static libraries of a107 
is because we are busy working on a108, not because of any other 
restriction.

Is that an official statement?

I can't make that, but haven't heard anything that implies otherwise.

This all seems very cutting edge so I expect anything could change 
(i.e. alpha).

It is cutting edge indeed :)

so much it bleeds  ;-)

Hmm... REBREQ looks very familiar.. very much like the Amiga's standard 
IO request :-)

hehe... that's not where similarities end ....  ;-)

Besides the r3 core, what other bits would RT be providing for these 
kits?  include files?

What you see in the .tar.gz is the complete hostkit. Sources, headers, 
and the proprietary libr3 binary blob.

so the idea would be to create sub-dirs with whatever platform-specific 
stuff needs to be there... simple

oh, and a makefile I expect (or whatever build system)

Yes. But the makefile provided with the Linux hostkit (in make-gcc/) 
should get you pretty far.

I think gmake is a good common denominator these days for build systems

Agreed. The current makefiles are written for a much lower common 
denominator, though.

lower than gnu make?