AltME groups: search

If you want to see how the boot.red script is compiled, use:

    do/args %red.r "-v 2 %red/tests/hello.red"

double clicking red.r in the root causes the same error .....

Two notes:


- when in root directory, where %red.r resides, is there a need to 
specify it in compilation process? do/args %red.r - or do we expect 
more compilers here?


- executable is spilled out into the root too. I would probably use 
the way compatible to red/system, and create /builds subdir?


Or is all above intentional to allow to compile/link from working 
dirs?

I did this 
$ git clone https://github.com/dockimbel/Red.git

so how come red.r doesn't come down?

# rebol -qw red.r %red/tests/hello.red

-= Red Compiler =- 
Compiling red/tests/hello.red ...

...compilation time: 	 30 ms

Compiling to native code... 

...compilation time: 	 1282 ms
...linking time: 	 	 25 ms
...output file size: 	 	30912 bytes

# ./hello
42

hm.. now it works here as well even with the name foo... maybe I 
just fooled the compiler as I compile from REBOL console using:

do/args %red.r "-v 0 %red/tests/console.red -o %../builds/console"

so possibly if there was some error before, the compiler state was 
not cleared

FYI, my plan is to get rid of %rsc.r and merge its features to %red.r 
(deciding on the compiler to use based on input script header). The 
%red.r  front-end is smarter and able to better handle relative paths.

+1 for the merge of  %rsc.r into %red.r . Never liked the name %rsc.r

@Kaj, The Yen sign has disappeared here! Congratulations! :)

I would still like the default output to be deposited in the working 
directory, instead of the builds directory

 I think I agree with this. In the ideal situation you could specify 
 these things, maybe in a settings file or in a preference in a compilation 
 assisting program. (Started one once)  

The integration of rsc.r within red.r sounds as a logical step. (rsc.r 
Red System Compilation, not so bad and a clear difference from red.r 
for Red scripts)

Doc: "did you encapped Red compiler?" Nope, RedCompiler.exe is just 
calling the rsc.r or red.r according to the extension of given script 
file. It should be placed in the red-master directory.

I tried to make a encapped Red compiler but there are some problems 
with #include or other compiler directives.

Once we merge %red.r and %rsc.r, I will look into encapping the whole 
thing, so we'll be able to start distributing Red as a unique binary 
file.

I might miss some basic OS understanding. Guys, how do you work with 
all the path? I have JAVA installed, REBOL installed, yet what I 
am strugling with, is path. When I follow docs, it always seems to 
be easy. Docs state:


do/args %rsc.r "-dlib %bridges/java/JNIdemo.reds -o %bridges/java/JNIdemo"


well, for normal user, in order to try that, user needs to understand, 
he has to start Rebol for that. So there are basically two options:


- running REBOL from icon. Then you have to change-dir to where Red 
is - in my case, something like C:\!Rebol\Red

- I thought, I might use just "pressing ENTER" upon Red.r, which 
launches console for me. But above still will not work, unless I 
change-dir into red-system subdir. It should be imo either stated 
in the docs, or some shortcuts provided, e.g. red-system.r, allowing 
me to launch console directly in that subdir, and then above command 
would run just OK.


I am not stating anything is wronk, it is upon user to improve the 
workflow, but surely it is an obstacle for occassional user.

Now back to docs:

2. Compile and run the JNIdemo.java app from console:

        $ javac JNIdemo.java
        $ java JNIdemo


Well, when in console, my console does not recognise javac, nor java 
executables. Apparently a path problem, but I have JAVA installed 
via installer. So I have to go inside JAVA dir, which means:

cd c:\Program Files (x86)\Java\jdk1.7.0_21\bin\
javac c:\!rebol\!Red\\red-system\bridges\java\

Any tips? :-)

I don't understand the part of your post that starts with "I thought, 
I might use just "pressing ENTER" upon Red.r"

and I can find red.r in the main directory. Whne I hit enter, it 
just launches the console. But maybe I am missusing it :-)

I am runing %red.r for %0MQ-request-client.red but failing on 
#include %../common/common.red
It looks like it would be from 
https://github.com/dockimbel/Red.git
but I don't find any common/ directory

I am probably mis-aligning my zmq directories but don't have anything 
but common.reds from clones.
Any hints to help me find my path?

either I have mess again on my system, or there's a compilation error 
for me, when trying to do:


do/args %red.r "-dlib -v 0 %red/bridges/java/hello.red -o %../red/bridges/java/hello" 


Script: "Red/System IA-32 code emitter" (none)
*** Compilation Error: missing argument
*** in file: %structures.reds
*** in function: exec/~java-instantiate-abstract
*** at line: 166
*** near: [jni-env/jni/NewObject]

Gregg Irwin has rewritten the redcompiler.r script on rebol.org and 
I now added a help screen, a check for a red.r compilerscript in 
the selected directory, support for Red source only compilation, 
the option --red-only Doc recently added. 

You can still find the new script here http://www.rebol.org/view-script.r?script=redcompiler.r