World: r3wp

With Host kit how do we role our own R3 code into the builds?

there is a function in rebol-lib.h which is called Reb_Do_String(); 

you could use it to run a bit of code in host-main.c BEFORE this 
line:


 n = (Main_Args.options & RO_NO_BOOT) ? TRUE : Reb_Start(0); // TRUE 
 on halt

there are few other funcs there which are intriguing.



but you can't add native stuff yet anywhere in the host.. for that 
we have to wait for Carl to move the extension code to the host first.

ok, so right now only build the core module and that is all right?

yep, once your IDE is setup it should compile as-is.  it did for 
me, the first time tried.

cool

do follow the instructions here: http://www.rebol.net/wiki/Host-Builds#MS_Visual_Studio

( I'm using visual studio express, which is free, and it works without 
hassle)

Yeah, I got those.  I got studio installed already so I will be building 
it shortly.  I may do it tomorrow.

Max - the first REBOL developer productively moving to R3 :-)

The 2nd.

Cool :-) How's your SQLite driver progressing?

Done. Now adding multi database handling &  SQL statement caching 
and than that's it. Don't have an idea what to add else.

Do yo use lib, or do you wrap DLL? = if you are using lib, you need 
to rebuild extensions for each new SQLite release. But I understand 
that statically linking might be easier ...

Robert - you know what was missing in R2 SQLite driver? Collation 
support. We (me, Ashley) tried to find out, how to use it, but were 
not able to wrap collation routine in R2 DLL interface.

I use the static lib and compile everything into one DLL.

Update for new SQLite verison is simple.

Collation: Not looked at it yet. I have never needed it.

so you don't need to correctly sort in German language?

Well... ;-) Yes, I do.

Will take a look.

I think the instructions for the Visual studio host kit instructions 
needs to be modified a bit more.  I'm a newb to Visual Studio but 
found the instructions confusing for the adding of the additional 
files and for finding the "additional include directories"

needless to say the build failed for me and I suppose that is because 
of file locations.  This is where it crapped out:

1>LINK : fatal error LNK1104: cannot open file 'r3lib.lib'

I stopped programming games in c/c++ because IDE-s for it have so 
damn many settings.. getting things to compile was harder for me 
than program them

Yeah, I may try something else.

it's not that hard for simple projects once you get the hang of it..

Janko, same here :-) I found it odd that there were so many 500 page 
"Get started with Visual Studio" book around, when I tried it.

simple meaning with hacving few .lib-s

:) "get started"

Yeah, I'm sure my build is because of how I'm interpreting the instructions 
given.  It says "Add all the .c files from src/os and src/os/win32. 
"  I didn't know how to add them.

Janko: I barely got started with the C++ course I took. It was a 
failure, because we were stuck with that IDE. It was really about 
which buttons to push, just to make an app.

Also it says  " In Linker/Input: add r3lib.lib and wsock32.lib to 
the Additional Dependencies ".  I just added both of the file names 
- not sure if I needed path statement also or not.

I forgot a little but you need to add directories where it will look 
for libs .. like include paths.. this is not per project setting 
I think (at least vasn't in VC6)

Yeah, I added that section as the instructions stated.

I generally don't like IDE-s .. simple text editor with some colors 
and I am happy ... :)

I went ahead and built the host build using mingw.  This was a breeze 
in mingw.  However, I suggest updating the documentation to just 
update your path statement to include a path to mingw/bin and instead 
of copying mingw32-make.exe to make.exe just go to your r3 host build 
directory and type mingw32-make.

Paul, if you've got any questions, I've played around A LOT with 
the install instructions, since I now have a solutions with 3 projects 
and inter project dependencies...


its the first time I really use visual C, so it wasn't obvious to 
begin with, but I do understand most of it now.  it took me a few 
hours to get this new setup working with the host, the extensions, 
my OpenGL extension and the callback thing.

I've replaced all the paths by using the various $(...)  macros.

I only use the IDE for debugging and compilation... I actually do 
all the coding within Ultra-Edit, its just sooooo much better for 
editing.

Maxim, for newbs to Visual Studio like myself, I think we need more 
hand holding on the install instructions for that part.  Maybe you 
can make some recommendations to make it more painless and targeted 
toward the newbie.

but being able to click on words and get the line they where defined 
in other files loaded automatically is very usefull when debugging... 
also for the tracing of error and warnings..

yeah.  You sound like your not a newbie to VS

somehow I found it explicit... I added the info about unicode, cause 
sometimes, the VS creates projects in unicode, sometimes not... strange.

ahhh good.  We just need to make sure these instructions are as brief 
but efficient as possible.

actually, I only started using VS last week.


when I did my previous Extensions test, I used VS, but didn't play 
at all wit it... I had used the whole project supplied by carl.

but having a page with screen grabs would be much better.

Yes, I agree.

The thing with  MinGW is to get this installation right. Which is 
far from easy, like the make stuff shows.

For me the host-code was simple to compile: make

That was it, worked on the first shot.

But I didn't have mingw in my path.  I think that was the problem.

Ah, that would do it. The MinGW installer says it's going to set 
the path, but it fails at doing so. You have to do it yourself.