After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 356416 - Library support broken
Library support broken
Status: RESOLVED OBSOLETE
Product: anjuta
Classification: Applications
Component: plugins: project-manager
git master
Other All
: Normal major
: ---
Assigned To: Naba Kumar
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-17 17:11 UTC by Johannes Schmid
Modified: 2020-11-06 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Johannes Schmid 2006-09-17 17:11:38 UTC
Please describe the problem:
Library support does not work in the moment. If you want ot add a library target nothing or nothing useful is done to the Makefile.am

The involves also checking for AM_LIBTOOL and such things in configure.in

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Günther Brammer 2006-09-22 14:22:49 UTC
Should gnome-build really edit configure.{in,ac} to add AC_PROG_RANLIB or AC_PROG_LIBTOOL? That file can contain arbitrary shell script, which could easily mislead gnome-build.
Comment 2 Johannes Schmid 2006-09-22 14:33:43 UTC
Hi Günther!

Well, gnome-build already parses the PKG_CONFIG macros in configure.in/ac and is able to modify them. Of course we can only handle the most common cases but that should be enough for most projects.

Johannes
Comment 3 Johannes Schmid 2007-01-31 22:33:10 UTC
I recently found out that libraries will work in gnome-build. The problem is that you have to correctly guess the name libtool wants to have for a library and this can be really difficult. We need a good way to check for the name and give advice to the user.
Comment 4 Naba Kumar 2007-02-01 08:57:05 UTC
Wasn't there a bug also where we thought having validation (done by the backend) would be a way to prevent wrong target names?

As for adding/removing AC_PROG_RANLIB and/or AC_PROG_LIBTOOL can be easily done in configure.(ac|in) file. It probably doesn't matter where we insert them, but some rudimentary checks can be done such as just after one of the some pre-decided macros.
Comment 5 André Klapper 2020-11-06 20:21:46 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue 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 fixed.