Bug 7732

Why is it not possible to select "incremental" build when in project "enable debug" is not selected? 13 January, 2022

Miguel Leeuwe
03 January, 2022
Product: PowerBuilder Category: Compiler
Version: 2021 Build: 1311
Classification: Unsupported Publishing: Public
Priority: P3
Status: Closed Reason: CANCELLED
Mark Lee @Appeon 13 January, 2022
#12
Yes.
Miguel Leeuwe 13 January, 2022
#11
No problem.
I've watched your video and just to be clear, my last question: 
In this compilation, as shown in the video, without the checkbox in the project being marked, will "DEBUG conditional blocks" be interpreted correctly or not?
regards
Mark Lee @Appeon 13 January, 2022
#10
vedio

Sorry for forgetting it.
Miguel Leeuwe 13 January, 2022
#9
Hi Mark,

"In addition, according to our internal discussions, we will deal with these compilation-related issues in a unified manner when refactoring this function in future versions". Okay, it's good to hear this is going to be less confusing in the future.
BTW: You didn't attach any video.
regards,
MiguelL
Mark Lee @Appeon 13 January, 2022
#8
Hi Miguel,

Sorry that the previous reply was wrong.
"Incremental Build"... means that only objects whose ancestors have changed will be rebuilt.
The execution of the "Incremental Build" or "Full build" function is not directly related to the deployment settings in the project object.
 
In addition, according to our internal discussions, we will deal with these compilation-related issues in a unified manner when refactoring this function in future versions.
For the log message, you can check my video in the attachment.


Regards,
Mark Lee
Miguel Leeuwe 12 January, 2022
#7
Hi,
Quote: "although you can still choose "Incremental Build"... but in reality, this incremental compilation will not work properly."
If that's the case, then it shouldn't be possible to do an incremental build using the right mouse button. Once it starts, it should check the project and give an error message and stop. I think that should be fixed because a lot of users don't know about this. They'll think they've done a correct incremental build!
Where's this log message?
regards
Mark Lee @Appeon 12 January, 2022
#6
Hi Miguel,

Thanks for your confirmation.
According to my test, if you are sure that there is a project with Full Build and DEBUG is unchecked in your project, although you can still choose "Incremental Build"... but in reality, this incremental compilation will not work properly. The relevant log information can prove what I said.
 
So based on previous analysis, we will close this ticket. If you have other questions, please open a new ticket.
 
Thanks for your understanding!

Regards,
Mark Lee
Miguel Leeuwe 06 January, 2022
#5
withRightMouseClickIcanStillDoIncremental.png (60KB)

One last thing: I DO wonder what happens with the things you explained if:
- I have a single project object, which is set to do Full Build and DEBUG is unchecked.
- I then do a click with right mouse button and can still choose "Incremental Build" ... 
Would that get around the problems that you described or would that cause errors if DEBUG is used in the code?
Miguel Leeuwe 06 January, 2022
#4
Hi Mark,
Thanks for looking into this. I was just curious and thought there might be an easy fix. It's not worth the trouble to change it. When we create an executable for release, we would ALWAYS do a Full build anyway.
Please close this ticket,
best regards.
Mark Lee @Appeon 06 January, 2022
#3
Hi Miguel,

We reviewed the relevant code, and the reason seems to be that the incremental build cannot handle the conversion of DEBUG code blocks to blank lines timely. As this design is intentional, there is no plan to modify it at this point. For the time being, we suggest that you keep using full build or check Enable DEBUG Symbol check box for the incremental build.
 
BTW, here is the documentation for Enable DEBUG symbol:
When a project's Enable DEBUG Symbol check box is selected, code is fully parsed by the compiler and included in the deployed application. The code is converted to blank lines when the check box is cleared. The DEBUG symbol is always defined in the development environment.
 
When you run or debug the application in the development environment, the code is always parsed and you always see the message box. When you run the executable file, the code is parsed only if the DEBUG symbol is enabled on the General page in the Project painter. While you are still testing the application, turning the DEBUG symbol can help you find differences in behavior in the development environment and the executable file.
https://docs.appeon.com/pb2021/pbug/Debugging_and_Running_Applications.html#Using_the_DEBUG_preprocessor_symbol
 
Limitations
You must rebuild your application after you add a DEBUG conditional block.

Regards,
Mark Lee
Miguel Leeuwe 03 January, 2022
#2
TY
Chris Pollach @Appeon 03 January, 2022
#1
Hi Miguel;

   Thank you for opening this ticket. I will now transfer this immediately over to the Engineering team for feedback as to the circumstances as to why this behaviour is being observed by the IDE.

   For the future though, I am hoping that the upgrade to a newer C++ compiler in PB2022 will allow Engineering to maybe address this restriction. Let's see what they say.

Regards .... Chris
Miguel Leeuwe 03 January, 2022
*Phenomenon: As decribed in the title.
Please see: https://community.appeon.com/index.php/qna/q-a/why-is-it-not-possible-to-select-incremental-build-when-in-project-enable-debug-is-not-selected
regards,
MiguelL

*Reproduce Steps:


Remarks:
OS:
Windows 10
Platform:
64-bit
Database Type:
Database Version: