AltME: R3 Building and Porting


florin: yes, it's possible to include embedded modules or embedded extensions with R3. but it's not documented how to do so, at the moment, so you'll have to dig through the sources yourself.
for embedded modules, it could be as simple as dropping your module in src/mezz/, including its filename in src/mezz/boot-files.r and doing a full rebuild (including `prep`) after that. didn't try yet, though.
Florin, I wrote this about adding your own scheme
GrahamC: Wonderful, thanks.
That's what I did for my vanity builds for integrating the time and smtp schemes
see the vanity group here

Has anyone tried building R3 on Windows with CodeBlocks? I want to run R3 in debug mode, to track down native bugs.
I can also use VS2012 Pro, but it's less likely that someone has tried building on that. One can hope, of course.

Just so happens that I have a CB project file for the official source layout, if you want it. There's also a little change to make-make.r that you'll need t make for which he's made a pull request.
Sent you the file
btw, there's currently no difference between the release and debug targets - CB just builds the all target with whatever flags were there. We could change this to create distinct builds, obviously.
put the project file in the root of the project - sibling to the .git
"for which he's made a pull request" -> "for which Andreas has made a pull request"
Thanks. Andreas helped set me up with VS2012 builds. I'll get to CB later, I'm sure with the help of your project.

I'm trying to learn a little more about debugging to figure out what is happening with the TCP bug
(On Windows), I've built a rebol with symbols included and I have reached segmentation faults with rebol several times
using GDB
Using backtrace, I can see the following:
Program received signal SIGSEGV, Segmentation fault.
0x76f0579c in ?? ()
(gdb) bt
#0  0x76f0579c in ?? ()
#1  0x76f055c5 in ?? ()
#2  0x76f8cc48 in ?? ()
#3  0x76f385ff in ?? ()
#4  0x76f055c5 in ?? ()
#5  0x75199b9c in msvcrt!malloc () from C:\Windows\SysWOW64\msvcrt.dll
#6  0x00421363 in Make_Mem ()
#7  0x00421814 in Make_Series ()
#8  0x0042d5fb in Make_Binary ()
#9  0x0042bc16 in TCP_Actor ()
#10 0x00409a10 in Do_Port_Action ()
#11 0x0040922a in Do_Act ()
#12 0x00409364 in Do_Action ()
#13 0x00404457 in Do_Next ()
#14 0x00404d45 in Do_Blk ()
#15 0x004235c3 in N_switch ()
#16 0x0040914f in Do_Native ()
#17 0x00404457 in Do_Next ()
#18 0x00404d45 in Do_Blk ()
#19 0x004093ae in Do_Function ()
#20 0x00403bbf in Apply_Function ()
#21 0x00403c66 in Apply_Func ()
#22 0x00425122 in N_wake_up ()
#23 0x0040914f in Do_Native ()
#24 0x00404457 in Do_Next ()
#25 0x00405a5f in Do_Args ()
Trying to learn how to investigate the structures to identify where it's going wrong
Anyone else have any scripts they have had bugs with tcp that I could look through.

Last message posted 91 weeks ago.