Skip to content

Comments

refactor: avoid writing into src dir upon building#2452

Open
mmagician wants to merge 2 commits intonextfrom
mmagician-build-skip-src-write
Open

refactor: avoid writing into src dir upon building#2452
mmagician wants to merge 2 commits intonextfrom
mmagician-build-skip-src-write

Conversation

@mmagician
Copy link
Collaborator

@mmagician mmagician commented Feb 16, 2026

Avoid writing to src dir upon building.
Instead, write into OUT_DIR and include the generated files.

Related to #994

@mmagician mmagician added the no changelog This PR does not require an entry in the `CHANGELOG.md` file label Feb 16, 2026
Base automatically changed from pgackst-test-fast to next February 17, 2026 08:02
@mmagician mmagician force-pushed the mmagician-build-skip-src-write branch from d703d7b to 279ee0d Compare February 17, 2026 10:20
@mmagician mmagician changed the title refactor: avoid writing into src refactor: avoid writing into src dir upon building Feb 17, 2026
@mmagician mmagician marked this pull request as ready for review February 17, 2026 10:22
Copy link
Contributor

@Mirko-von-Leipzig Mirko-von-Leipzig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice does this mean I'm allowed to do the same with the proto files 😬

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does one need to copy source files into {OUT_DIR} as part of the build script?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure either. Maybe because we previously wrote into the src directory and didn't want that to interfere with the assembly process? I think we could try skipping the copy and try building directly from src and see what happens.

Copy link
Contributor

@PhilippGackstatter PhilippGackstatter left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

I think this would make rebasing and merging a more convenient due to fewer conflicts in the generated files, which are no longer committed. Also, we shouldn't run into the re-build issues anymore as fixed in #2448 most recently.

@mmagician mmagician added the pr-from-maintainers PRs that come from internal contributors or integration partners. They should be given priority label Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no changelog This PR does not require an entry in the `CHANGELOG.md` file pr-from-maintainers PRs that come from internal contributors or integration partners. They should be given priority

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants