Application Compiler

K

kilencvenot

New Member
Hi Talkers,

I'm new with this technology, and, I think I need a little help from you.

I've got a lot of sources codes, in many dictionaries, linked with relative paths to each other.
I've tried to compile them, as it is written in the documentation, but, I think I meda something wrong.
If I used the new dictionary option, then, the compiler was unable to work, because the whole set of dictionariers doesn't exist. I have to create it manually?
Or, if the sources and the compiled procedures are in the same dictionaries, I have to delete the sources manually?
I hope you already know what my problem is, I'm sure it is the problem of the absolutelly beginners, and the compilation can be done automatically - somehow.

Many Thanks,

Thomas
 
Thomas,
the compiler first looks in the current work directory for the source file,
if file not found it then scans the PROPATH,
if relative paths are used in source files, the compiler adds the relative path to:
1)st to current directory 2)nd to each PROPATH element
 
Hi,

The sources are on the propath, and the complier creates the r codes to the same directories.
That means I've to delete manually all the source files?
I've tried to set up the "save into" setting, but, if the codes are in a difficult directory structure,
I have to create it manually?

Thomas
 
the compiled files(.r) can all sit in same folder,
if there are too many of them (e.g: >1000), to minimize the overhead time to locate the file,
you can split them in few sub-folders, following some logic (e.g: according to first two letters)
Progress/OpenEdge engine must be able to find them either with Propath, or by specifying
the full subfolder path (relative to one of Propath folders) on the RUN statement.

I usually compile using the "SAVE INTO" option, so the (.r) file saved into different folder than the source(.p) file
 
You must log in or register to reply here.
Back
Top