GNOME Bugzilla – Bug 642785
New autotools backend has problems with custom m4 macros defining subdirs
Last modified: 2020-11-07 12:12:53 UTC
Created attachment 181368 [details] Screenshot of the issue See attached screenshot. reproducable with git.gnome.org/rygel.git, also http://git.gnome.org/browse/rygel/tree/m4/rygel.m4#n31 http://git.gnome.org/browse/rygel/tree/configure.ac#n171 We use the custom macro RYGEL_ADD_PLUGIN to conveniently add a --enable-foo option plus calling AC_CONFIG_FILE
Could you detail the issue here? I have loaded rygel with the latest version and it looks quite good except the missing sources in rygel target (reported as bug #642784) It is possible that I have fixed this issue since you report it.
No, still there, with becf46b.
What is the issue? By example here, I have under rygel/src/plugins/gst-launch a target named librygel-gst-launch.la with 5 source files below. Should we have something more?
That's odd. I don't see this, the dirs are empty for me, even after re-importing.
(In reply to comment #4) > That's odd. I don't see this, the dirs are empty for me, even after > re-importing. Ok, I have updated my version of rygel and I get the issue now. It seems that the backend doesn't like your cleanup and simplification :(. I'm checking what's happen.
That's what I feared. On the other hand, I'm not really sure if the back-end has to support this kind of projects
Yes, I understand the issue now and indeed that's the question. The source of gst-launch plugin by example doesn't appear because anjuta hasn't found the Makefile.am file because it's not listed in the AC_CONFIG_FILES macro. In fact, the makefile is added in AC_CONFIG_FILES but through the macro RYGEL_ADD_PLUGIN. Anjuta doesn't support such thing currently. The issue is that I don't know how to handle such case. I think supporting such thing will need to rewrite most of m4 and some parsing code from autoconf. It's even much more complex, because Anjuta is supposed to be able to modify the file which is not done by autoconf. I'm really going in this direction as I have written a real parser instead of just modifying the file using regular expressions. But I don't plan to support every possibilities. My goal is to fully support only basic projects, like the one created by Anjuta. Then, perhaps the best answer is just to use the directory backend for such case. Anyway, I don't have the solution. For the moment, I still need to improve the project backend because it still fails on much simpler case. But then perhaps we can check how to improve the situation.
Maybe we turn this into a feature request?
Yes, for sure. Then I'm wondering how much people will use such feature but perhaps it's not so difficult to implement.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old feature requests in Bugzilla which have not seen updates for many years. If you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/anjuta/-/issues/ Thank you for reporting this issue and we are sorry it could not be implemented.