You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 secondgoa build
, however, restored the original version. Since./configure
will be skipped if config.status already exists, the secondgoa build
used the wrong Makefile and always failed.The text was updated successfully, but these errors were encountered: