tim-janik / rapicorn

Rapicorn is a toolkit for declarative UI construction and SVG-based theming
https://rapicorn.testbit.org/
Mozilla Public License 2.0
12 stars 2 forks source link

Missing .m4 files from the released tarball for 16.0.0 #9

Closed GvMariani closed 8 years ago

GvMariani commented 8 years ago

To resolve the Issue #8, it was needed to patch configure.ac (and configure); this usually requires also to regenerate the configure script. However, with the tarball from https://testbit.eu/pub/dists/rapicorn/, the autoreconf pass fails at the very start, because acrapicorn.m4 and ld-symbolic.m4 are missing:


Also, trying to be clever and to workaround the problem by patching configure without regenerating it, it does not work; in this case the build fails at the very start of the make phase:


The tarball provided by GitHub release page, however, has all the needed files.

tim-janik commented 8 years ago

Hey GvMariani, regenerating the release tarball configure script from just the release tarball isn't really supported. We simply generate it from the Git sources via autogen.sh, a full build and make distcheck. If you want to patch configure.ac, you need to apply that to the checked out git sources and build the tarball similar to our travis builds. I'll quote the relevant bits from .travis.docker for you:

nice ./autogen.sh --prefix=/usr --enable-devel-mode=no nice make -jnproc nice make check nice make install nice make installcheck nice make distcheck

I'll look into applying a fix for #8 next.

GvMariani commented 8 years ago

Thank you for your kindly reply... Well, I don't know about too many projects, but usually I found that is OK to regenerate the configure script from the release tarballs, if needed, with a simple "autoreconf -vfi". With rapicorn it is not the case, but my way to solve issue #8 required patching configure.ac (and consequently regenerating configure), and I guessed wrong...