' Rapid-Q by William Yu (c)1999-2000                                             .
' ================================================================================
' Upload_il_tuo_script_su_Rapidq.it

' relative_paths_in_rapidq

****** Overriding path issues ******
One of the most boring things, when you download a source code, is loosing time
changing the paths for resources. When you compile your programs, instead, you
have to put your source code in the same folder of the ocmpiler. Is it the only
way ? No.
****** Step 1 - Files and folders ******
First, we have to give a "structure". Generally, you the following
files in the "RapidQ" folder:
    * RC.EXE
    * RAPIDQCC.LIB
    * RAPIDQ32.LIB
    * RAPIDQ2.LIB
    * RAPIDQ3.LIB
    * RAPIDQ4.LIB
    * RAPIDQ2C.LIB
    * RAPIDQ3C.LIB
    * RAPIDQ4C.LIB
    * RAPIDQ.INC
    * WIN32API.INC
If you have not RapidQx.lib and RapidQxC.lib files is because they are not
really necessary. Think about them as "splits" of the main Rapidq32
& RapidQCC. Ok now you have to make a subfolder for inc files and one for
Lib files. So now you have something like C:\RapidQ\Lib and C:\RapidQ\Inc
Move the lib files in the "Lib" folder (... and the inc files in the
"Inc") folder.
****** Step 2 - The many ways to run the program ******
To call the compiler from anywhere, you have to run it as:
  &quot;C:\RapidQ\rc.exe&quot; <SOURCEFILENAME> -L&quot;C:/RapidQ/Lib&quot; -
                          I&quot;C:/RapidQ/Inc&quot;
This is the general form. Of course you have to substitute paths with your own
ones. There are some things to keep in mind.
    * Better if you pass complete paths
    * Always quote paths (enclose them in &quot; and &quot;)
    * Leave no blank space between -L and the quote
    * Leave no blank space between -I and the quote
    * Better if you use slash ( / ) in paths
    * For the compiler path, instead, use backslash ( \ )
    * ALWAYS set working dir to source code dir
    * File name path must be absolute.
 
You can use these &quot;rules&quot; to make a batch file, compiling your
program. Or, if you like, Make a link and put that info inside the lnk file
(always set up source code folder as working folder). You can even integrate
the general command line with your code editor.
 
If you use Context
-----------------------------------------

- Open Options >> Environment Options

- In the &quot;execute&quot; edit put &quot;rc.exe&quot;

- in the &quot;Start in&quot; field put the path of rc.exe

- For &quot;Parameters&quot; put %n -L&quot;./__lib&quot; -I&quot;./__inc&quot;
where __lib and __inc are the directories where you
put lib and inc files.

- If you want to put your compiled programs in a specific folder
Parameters should be

%n <yourfolder>\%F.exe -L&quot;./__lib&quot; -I&quot;./__inc&quot;

If you use JFE
-----------------------------------------

- Application -> RC.EXE

- Start directory -> the directory where rc.exe is

- Parameters -> $PATH\$FILE -L&quot;./__lib&quot; -I&quot;./__inc&quot;
where __lib and __inc are the directories where you
put lib and inc files.

- If you want to put your compiled programs in a specific folder
parameters should be

$PATH\$FILE <yourfolder>\$NAME.exe -L&quot;./__lib&quot; -I&quot;./__inc&quot;
 
****** And now ? ******
Now you should be able to compile your source code anywhere the files are. But
not only
    * You can put all extended components (generally distributed as
      &quot;inc&quot; files) in the inc folder, so that they are always
      available (like QVideo, QListviewEx,...)
    * You can use relative paths in your source code (and you can compile
      programs with relative paths)
    * You can have each project in a separate folder.



' ===============================================================================
'                      2003 Holyguard.net - 2007_Abruzzoweb