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

automake fails with sourceforce release tarball #59

Open
umlaeute opened this issue Nov 6, 2024 · 4 comments
Open

automake fails with sourceforce release tarball #59

umlaeute opened this issue Nov 6, 2024 · 4 comments

Comments

@umlaeute
Copy link

umlaeute commented Nov 6, 2024

  1. visit https://github.com/x42/xjadeo
  2. notice that it links to the "official" homepage http://xjadeo.sf.net/
  3. on the sf page go to downloads
  4. scroll down to get the download to the source tarball http://sourceforge.net/projects/xjadeo/files/xjadeo/v0.8.14/xjadeo-0.8.14.tar.gz/download
  5. download it
  6. extract the sources
  7. run autoreconf -fiv
$ autoreconf -fiv
[...]
configure.ac:443: error: required file 'src/qt-gui/Makefile.in' not found
configure.ac:443: error: required file 'src/qt-gui/qjadeo.pro.in' not found
[...]

(I'm running autoreconf, as the autogen.sh mentioned in the README is missing from the source tarball)

The problem is obviously, that the source tarball has no src/qt-gui/ folder.

I see that there is such a folder in this repository, but it has been stripped from the release tarball.

@umlaeute umlaeute changed the title autoconf fails with sourceforce release tarball automake fails with sourceforce release tarball Nov 6, 2024
@x42
Copy link
Owner

x42 commented Nov 6, 2024

That is odd. looks like you've used enable_qtgui in the past.
That setting is disabled by default, so autoreconf should not reach that code.

x42 added a commit that referenced this issue Nov 6, 2024
This external control UI has been deprecated ever since there
is a native built-in X11 GUI.
@umlaeute
Copy link
Author

umlaeute commented Nov 6, 2024

That is odd. looks like you've used enable_qtgui in the past.

???
this is from a fresh clone.
(also i typically build 3rd party code in throw-away containers, so ...)

That setting is disabled by default, so autoreconf should not reach that code.

note that i'm talking about autoreconf (resp. automake which is what is called under the hood).
as such, all the m4-code protecting

AC_CONFIG_FILES(src/qt-gui/Makefile src/qt-gui/qjadeo.pro)
with
if test "$enable_qtgui" = "yes"; then
is rather pointless - as this code is never executed (it will get executed when running ./configure; but right now we are not there yet).

but i guess that ead81da fixes it anyhow :-)

@x42
Copy link
Owner

x42 commented Nov 8, 2024

Do you need a new release, or can you pick the fix from git?

@umlaeute
Copy link
Author

umlaeute commented Nov 8, 2024

No it's fine.
I've switched my scripts to now use the tagged archives from GitHub, rather than the source tarballs from SourceForge and reimported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants