World: r3wp

If you want just to try A110, go to REBOL3 GUI group here, there's 
a link to download a binary and dll .... we will have to wait for 
Carl to resurface and correct the release, or even better - to merge 
the changes to official location ...

The "carls-R3A110-a660e4a" release  works for me. You need to change 
in reb-to.h define# TO_WIN32 to get it work on Windows as Pekr said.

that did not help here ...

what error are you getting?

wait a bit ... I'll try to redownload Carl's HostKit

first - I am not able to get it downloaded via git client (Tortoise, 
nor normal), I get following error:

git.exe fetch -v --progress  "A110-Carl" 


fatal: http://github.com/carls/R3A110/info/refsnot found: did you 
run git update-server-info on the server?

you should probably clone it instead

Pekr, I tried it without the git client using this link: http://github.com/carls/R3A110/zipball/master

Downloaded .zip file. Tried it now - it works. It just does not seem 
to copy dll to the place of the exe, or something like that:

Linking executable: bin\Release\r3.exe
Output size is 317,50 KB
Running project post-build steps
post-build-win.cmd bin\Release\

Execution of 'post-build-win.cmd bin\Release\' in 'C:\!rebol\!R3\r3-host-kit-A110\make-cbp' 
failed.
Nothing to be done.

yes, the .cmd file is missing from some reason

I think that when Carl is back, we should merge. CC contains already 
some A111 fixes. What was the reason Carl posted the source tree 
in the different than usual place?

It's a test location

First, all make-* build methods except make-gcc are community contributed 
and not officially (i.e. by Carl) maintained. Therefore they may 
get out of sync, until someone in the community steps up and fixes 
them.

Second, the temporary R3A110 repository is even more unsupported 
than usual. Unless you want to work on distribution and building 
of the hostkit itself, it's probably better to stay clear of this 
and  wait until things settle down a bit.

Third, Pekr, you are _still_ using the wrong URL for your remote. 
Either make a fresh clone with

  git clone git://github.com/carls/R3A110.git


or fix your remote manually (Probably via `git remote set-url origin 
git://github.com/carls/R3A110.git`.)

anyone can help? Thx!

Aloysius - I already described the help, and Cyphre kind of confirmed 
- I noticed, that this hostkit is some linux version. When you look-up 
netdb.h, it seems its inclusion belongs to non-Windows #ifdef. So 
please go to /src/include/reb-to.h directory/file and rewrite the 
definition to: #define TO_WIN32

A quick note of success: just built an A110 hostkit on OSX Intel!

>> print system/version
2.100.110.2.5

Yay!

Is Carl still using his own personal repo?

Haven't heard anything from Carl for weeks.

So, there's still no official github R3 repo?

Nope, only the R3A110 test repo.

seems he's only available to blog comments .. all other channels 
are down

yes, another blac-out, which even SCRUM did not prevent us from .... 
nearly a month now, without a single message ...

Hey, he talks for 2 hours at AmiWest ...!

Selling his Amiga stuff? :-)

Yeah .. and in part 2, he says that people bug him everyday about 
Rebol ... lol

I still miss something like general R3 porting group. Or will we 
set-up one group per target platform here, as we did with Android? 
I think this group is good for technical host-kit stuff, not general 
porting stuff ...

I found out, that Genesi is now sponsoring Linaro Linux, which tries 
to unify distros for ARM target. They gave away 50 smartbooks:

http://bbrv.blogspot.com/2010/12/momentum-is-building.html
http://www.genesi-usa.com/products/smartbook


From past month's discussion with BBRV, I believe they are able to 
send us a machine to port R3. And now again - this is not my port-it-for-me 
request, just a note, to eventually start a discussion, how do we 
get ourselves on ARMs. Carl could have one smartbook to port Core, 
and someone willing to play with the HostKit port could have another 
one. In the case someone is interested, I could try to negotiate 
it with BBRV.


Of course - ARM is a broad term. I never heard of Linaro. We have 
some TI hardware, and I know there are some embedded systems for 
such stuff, mostly commercial and expensive, and Linaro might be 
an answer here. Another HW option is BeagleBoard (cheaper, more OSes 
supported, even QNX, Android):

http://beagleboard.org/

Pekr- thanks for the help, sorry my internet was so slow I didn't 
notice all the other chats until it was loaded just now. Thanks again 
for the quick response!

Porting R3 to an ARM netbook Linux would be a good start. The binary 
R3 library may then even work on Android

However, the Android cross-compiling SDK with its emulator is also 
a good development environment

Agreed.

Porting to a mainstream Linux ARM will hardly be any work at all.

Mostly a matter of either setting up a system to do the compile, 
or setting up a cross-compilation toolchain.

There will be some source changes, but probably not many

Talking about the hostkit side.

I imagine that some areas in the library, such as floating point 
support, may encounter some minor difficulties.

Me too. ARM is not a PC architecture, so there may be differences 
in the device drivers

Is there any plan to implement the serial port? I wanted to communicate 
with GSM modem via serial port for sending AT-commands. Thx.

Haven't heard anything about it, but I'm sure eventually someone 
will be interested in it

For such things it would probably be best to wait for the implementation 
of the devices interface, though

I was just recently thinking about serial port too, we will need 
it for kiosks. Maybe Carl could release R2 serial interface sources 
as a starter?

Let's say that I have a C++ application and would like to use R3.dll 
in it. Is there someone who is able to create a minimal example which 
would init R3.dll, send a string to it and get, for example, reversed 
output? I'm sure that such and example would help with R3 adoption.

I'll get to that when I start porting View to the Syllable GUI, but 
that project is still a bit in the future

Starting with literally just the dll is probably a unnecessarily 
complicated way to approach this.

The easier approach is to reshape the hostkit to embed it in another 
application.

The current "main" (src/os/host-main.c) is a good demonstration of 
what is necessary to init libr3 and eval strings.

Yes, of course