Uh oh, after realizing I needed to upgrade to the 2.78 sdk, I find myself without anything after paying with Paypal. Was there supposed to be another step? Usually one gets sent back to the site.
GrahamC
I think it usually comes as an email after a few days. But who knows if anyone is monitoring things.
Endo
I think they will send in a few days. I bouhgt my sdk license this year too.
james_nak
OK, great. Thanks. You know what I was thinking.
james_nak
FYI, I received my sdk license. All is well.
Endo
Did you download SDK version 2.7.8, in the mail I received there was a link to 2.7.6.
james_nak
It was 2.7.8 and it had all the various OS's
ddharing
Well, that proves there is still someone at the helm. I haven't communicated with RT regarding the SDK since last year.
james_nak
Yes, there is someone there at the other end. BTW, using 2.7.8 fixed all my issues.
Maxim
yes quite a few bugs fixed in 2.7.8 :-)
Henrik
When I run an encapped executable, I get the "Not enough memory" error. I remember seeing this before, but is it related to being unable to unpack the encapped source?
Henrik
rebooting windows helped.
Gregg
I haven't seen that in so long that I don't remember possible causes. I think there are values that cause problems when encapped, and also certain encap header values that can trigger it.
Maxim
serialized values get corrupted when encapped... which is why I had to rebuild my own prebol engine from scratch. I also wrapp my main source within a string, to be sure that the encap app doesn't corrupt my code.
Gregg
Thanks Max.
Maxim
(forgot to mention that I just just DO that string, which is the whole encapped source. basically equivalent to just running the script.)
so my script, once assembled looks like this:
rebol [ ... ] ; put what you want in the header
#include mezz/... ; whatever mezz code I need.
do { ... } ; the whole script, including results of my own extensive pre-processing toolchain