A
Anil Kumar
Guest
Hi romelwell, Following are some of the key options which will minimize the build process. 1. Turn on ‘Build only when source files are newer than r-code’ option in Project Properties page. This will compile only those source files for which no up-to-date .r files are present. This option can save time when compiled code already exists in the destination (rcode) directory. 2. Order of PROPATH entries in the PROPATH page and number of entries in the PROPATH page During the active development (this is not the case of force clean or manual Build operation): 3. Turn off ‘Build Automatically’ option in Project menu 4. Uncheck ‘Compile on save if required’ option in Preferences page Starting from 11.0 of PDS OE (aka OpenEdge Architect) there is an option to Exclude a folder/file(s) not to be part of the build. I.e., build process will not look for specific folder or files of folder during the compilation. Hope this helps. Thanks and Regards, Anil Kumar. From: romelwell [mailto:bounce-romelwell@community.progress.com] Sent: Tuesday, June 17, 2014 11:57 PM To: TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] Best practices to optimize compiler Build All feature in OpenEdge Architect? Best practices to optimize compiler Build All feature in OpenEdge Architect? Thread created by romelwell Is there any information detailing the best practices for using the 'Build All' feature in OEA? We have 613 files currently in our workspace (320 of the files are Include files) and it is taking the compiler ~6 minutes to build the workspace when a 'Build All' command is issued. We do not have a benchmark to compare this metric to and do not know if there are is compiler optimization patterns we should be pursuing at this time. Thanks. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...