1. Matt Balent
  2. PowerBuilder
  3. Tuesday, 14 February 2023 18:31 PM UTC

I see this old issue https://community.appeon.com/index.php/qna/q-a/modified-dates-of-all-pbds-were-updated-with-pbc190-i

I assume it was never reported as a bug?

In 2019 R3 2728 when I do an Incremental Build ALL the PBL files are rebuilt resulting in PBD files with the date the build was done.  In previous (at least in 12.5 or so) version only PBLs which had code or object changes were rebuilt.

Anyone else seeing this?

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 14 February 2023 20:26 PM UTC
  2. PowerBuilder
  3. # 1

Hi Matt;

  Yes, this PBD update was added & necessary to support the PowerClient feature in R3. This was also required for PB2021/2022 for use with PowerServer based apps as well.   HTH

Regards ... Chris

Comment
  1. Matt Balent
  2. Wednesday, 15 February 2023 12:21 PM UTC
So there is no way to do an incremental build anymore? (which was a useful feature btw)
  1. Helpful 1
  1. Chris Pollach @Appeon
  2. Wednesday, 15 February 2023 16:56 PM UTC
Hi Matt;



Yes, I do that in my STD Framework's Demo App as it compiles to Native 32/64 bit, M-Code + P-Code, then PowerClient 32/64 bit and finally PowerServrer 32/64 bit compiles. All the projects for these state "incremental". I normally start out with the 32 bit native P-Code compile. This typically will also perform a Full Build as I have quite often changed ancestor code (this over-riding the incremental setting). Then I leave the resulting PBD's within the WorkSpace main folder - even though I copy them to a "Deployment" folder for testing. With the latest PBD's now in the workspace area, the incremental 64 bit P-Code native compile & all the PC / PS 32/64 bit compiles go *super fast*. That is because the PB compiler can compare the P-Code that is in the PBL's to the local PBDs and make the decision on whether or not to perform any object builds to the PBD's.



Once I have compiled all of the above & copied the resulting compiled files to a "Deployment" folder, I delete all the EXEs, XML & PBD's from the workspace main folder. I then proceed to the M-Code compile last. If I still have the previous DLL's in the workspace folder, then this incremental compile goes much faster. If not, the IDE performs a Full Build (even though the project states incremental). Of course, this is much slower. Howevedr I now use SSD HD's on 16-32G of memory machines (W10 & W11) so even this has sped up the M-Code compiles substantially. BTW: My new machine is an AMD Ryzen 7 ... WOW - boot up time from cold (with sign in) - 15 seconds. M-Code complies are 1/10th the time. ;-)



Note that I always final QA test my code changes using the M-Code compiled App as copied into the Deployment Folder. If the M-Code runs 100% (as C++ is pickier to run), then I know that my PowerScript code is much more stable & faster. Thus the P-Code QA should be of the same quality.



HTH

Regards .... Chris
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.