Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent rebuilding due to replacement of generated files #119

Open
jschlatow opened this issue Feb 21, 2025 · 0 comments
Open

Prevent rebuilding due to replacement of generated files #119

jschlatow opened this issue Feb 21, 2025 · 0 comments
Labels
bug Something isn't working fixed Issue is resolved

Comments

@jschlatow
Copy link
Member

On every goa build, Goa symlinks the directory content of src/ into the build directory. In situations where the imported src/ contains files that will also be modified during the build process, this will always trigger a rebuild (at best).

When porting the autoconf-based curl, I encountered the situation that ./configure replaced the Makefile. A second goa build, however, restored the original version. Since ./configure will be skipped if config.status already exists, the second goa build used the wrong Makefile and always failed.

@jschlatow jschlatow added the bug Something isn't working label Feb 21, 2025
jschlatow added a commit that referenced this issue Feb 21, 2025
Upon build, the content from src/ is symlinked into the build directory.
If the build system replaces one of those symlinks with
a generated (regular) file, goa will restore the symlink on the next
build. For autoconf projects, this likely breaks the configure step.

Fixes #119
@jschlatow jschlatow added the fixed Issue is resolved label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed Issue is resolved
Projects
None yet
Development

No branches or pull requests

1 participant