Fix cmake test regeneration

[nishant11-tchy]

Summary

Improve CMake performance by avoiding unnecessary regeneration of test files during repeated runs.

Problem

Currently, test files are generated unconditionally via the p4_add_tests macro every time CMake is executed. This leads to slower build configuration times, even when no relevant inputs have changed.

Solution

• Updated the CMake logic to generate test files only when required
• Introduced conditional generation so files are not recreated on every run
• Ensured regeneration still happens when input files change

Result

• Faster repeated CMake runs
• Reduced unnecessary file operations
• No change in existing functionality or test behavior

Notes

• The fix is minimal and does not affect other parts of the build system
• Verified locally by running CMake multiple times and confirming no redundant regeneration

[nishant11-tchy]

Hi, I’ve worked on improving the CMake behavior to avoid unnecessary regeneration of test files.

The update ensures that test files are only generated when required, instead of on every CMake run. This helps reduce configuration time without affecting existing functionality.

I’ve verified the changes locally by running CMake multiple times and confirming that files are not regenerated unnecessarily.

Please let me know if any changes or improvements are needed. Thanks!

[fruffy]

There are 0 changed files.

[jafingerhut]

@nishant11-tchy I am not sure what is going on here, but given that you have two PRs with 0 changes, perhaps you are making changes to the main / master branch in your fork, creating a PR, then continuing to push additional changes to that same main/master branch in your fork? If you do that, it will affect all PRs using that branch.

That is why most github workflows for creating PRs say that you should create a unique branch name for each PR that you want to create. I'd suggest searching for github documentation on creating PRs that explain the sequence of commands required.