The short answer is the third-party tools would need to modify so they are no longer relying on the PBG since that is not generated.  To the best of my knowledge I think PowerGen is the only popular third-party build tool that has relied on the PBG.  My understanding is that they are committed to adapting PowerGen to be compatible with newer versions of PowerBuilder, so it's possible there is a newer version of PowerGen that is compatible or there would be one soon.  I would recommend contacting the third-party vendor.

Which 3rd party tool did you have in mind?

PowerGen from ECrane has an option to use OFL (object file lists) to match the source code to the PBLs.  With the latest release they added the option to create OFLs based on the ws_objects folder structure.  So you run that, and then you'll have the OFLs you need to do the build.

No - it appears the PBG file has gone away for the SCCS interface as well.

We are running PBSCC-Proxy and TortoiseSVN, to a SVN repository. From a Powerbuilder perspective the source-controls interface is SCCS.

Under PB2017R3 when I add an item to source control from the PB IDE the PBG file is not maintained.

Which will mean there is no way that other users - including our build workstation using ORCA - will import that new source item to their PBL.

I have not got my head around how much work there is for us to reconfigure for us to use the PB2017R3 SVN interface. And given our existing configuration has worked well I am reluctant to do that.

Sorry - I take that back - the above comment is inaccurate. The PBG file IS still maintained under the SCCS interface and PB2017R3 works exactly the same as PB2017R2. I had not examined the commit messages carefully enough to see the PBG file still being maintained when I responded above.

Hi Armeen, et. al.

A little background to PowerGen's use of PBGs...

We (E. Crane) introduced Object List Files (OLFs) before PBGs came out.  Because we needed a way to map object files to PBLs (what PBGs do) for our Bootstrap Import function.  Our Bootstrap Import was released a couple years before anything else like it existed.  (Yes we should have trademarked the term/process!)

From the beginning OLFs could either enumerate the objects or use wild cards in directory to map all the files in a directory to a particular PBL.

When PBGs were introduced, we supported them immediately in addition to keeping support for OLFs.

In fact we introduced functions to produce PBGs based on an existing set of PBLs.  We did this from demand from our customers who were finding the PBG files maintained by PowerBuilder would often get out sync with the application.

We have maintained support for all of this through all versions of PowerBuilder 2017 (and the new PowerBuilder 2019 Beta).  And have provided support specifically for the new source directory structure for the Git/SVN integration.

So PowerGen users with Git/SVN integration can either maintain PBG files for use with existing build scripts or use OLFs.

Regards,

Phil

Hi Arthur,

Yeah, it won’t generate any PBG file when using GIT/SVN SCC in PB 2017 R3 and PB 2019. Instead it uses the ws_objects folder. If you need the Object List Files, you can create it with the files in the ws_objects folder, i.e. if it is required to use a PBG in a third party software, you can utilize the ws_objects folder to create it on your own.

If you use PowerGen tool, it supports 2017 R3 and 2019.

Regards,

Ken

Coming to the Party a bit late on this.  My understating is that PBG files went away in PB2017 R3 regardless of what version control system you were using.  After reading this I am now a bit confused.  We can't upgrade to R3 because we are using an older Source Control called RCS which needs PBG... So the question is to confirm my original understanding.  Did PBG files go away, so for me to upgrade to R3 I would need to replace RCS is this True?

Thanks

Dave V.

Hi Arthur;

   **  Update **

   PBG files are still required on all PB2017R3 applications.  The prerequisite for needing the PBG file is when executing ORCAScript in PB 2017 R3 as it contains the location of the ws_object  folder generated by GIT/SVN. This is where all object files will be located for SVN/Git to process.

   You can get around needing the PBG(s) by specifying the localprojpath property in you ORCAScript file. For example ...

scc set connect property localprojpath ‘c:\dev\pb2017\orderentry’

Note that the ws_object  folder must be located under that localprojpath  property declaration.

HTH

Regards ... Chris