D
dbeavon
Guest
When I create a project in PDSOE, it may result in a sophisticated PROPATH. For example, a simple REST service will result in a .propath file with the following contents. One of the more interesting pieces to me is the PROPATH entry that was created for the "AppServer" folder (last thing in the sample below). This "@{ROOT}\AppServer" propath entry is created automatically, and is apparently needed for the "facet" (whatever that is) of the project related to ABL. My ABL programs within the "AppServer" folder are able to reference each other without explicitly specifying the "AppServer" folder name in the RUN or include statements. This is apparently because of the way the project uses that .propath file. How do I go about writing an ABL compilation command or script that compiles from the command line with the same .propath entries as used by PDSOE? I am getting the following error: ** "MyInclude.i" was not found. (293) Presumably this is because my compilation from the command line doesn't respect this propath data found in ".propath" . I haven't found any way to tell the COMPILE statement to use the ".propath" of the project in order to resolve unknown source references. Any help would be appreciated. I'm looking for a solution that is built on the Progress product (not PCT or something like that). I'd also prefer an approach that abstracts away the implementation of the ".propath" file so that I don't have to parse and interpret it myself (ie. let progress do that for me).
Continue reading...
Continue reading...