Re: Feedback on iProjects - good, bad and ugly

On Mon, Apr 24, 2017 at 9:37 AM, Edmund Reinhardt <
edmund.reinhardt@xxxxxxxxxx> wrote:

3) Improved build mechanism
- Simple compiles seem to work, If people are aware of RPGLEINC they can
avoid compiling their copy files.
- ILE is tricky for i Projects to guess correctly because it is not obvious
= we would need some additional metadata in the project to remember what
binds to what and with what compile/bind options
= we could possibly populate this from the existing compiled objects

​Can you elaborate on RPGLEINC?

First I recall hearing about it...

A quick google search turns up a blurb in the info center
"If the path does not end with a suffix (for example ".txt"), the compiler
will search for the file as named, and also for files with suffixes of
".rpgle" or ".rpgleinc".
​
​"
​
​It doesn't appear in the drop down for source member types....but it
appears to work and RDi appears to recgognize the RPGLE syntax in the
member...

So should our include members use RPGLEINC as a source type?

Thanks!
Charles​