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 399746 - naming conventions and makefile setup
naming conventions and makefile setup
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: documentation
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-23 11:43 UTC by Giovanni DG
Modified: 2007-01-23 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Giovanni DG 2007-01-23 11:43:12 UTC
The Pluging Writer's Guide misses a section on naming.
When someone needs to write a new plugin from scratch, it is ok to use the gst-template. But then the plugin name is not possibile to changed from "plugin".

The file Makefile.am in ../gst-template/src says:

# change libgstplugin.la to something more suitable
plugin_LTLIBRARIES = libgstplugin.la

if you change to
plugin_LTLIBRARIES = libgstmyplugin.la

make does not work any more, even after autogen/configure.

So you are stuck with 
libgstplugin.la

and could not change the binary library name.
Comment 1 Giovanni DG 2007-01-23 15:44:00 UTC
Just reading and understanding better the Makefile.am ...

# for the next set of variables, rename the prefix if you renamed the .la

;-)
Comment 2 Tim-Philipp Müller 2007-01-23 16:02:44 UTC
Thanks for the bug report. Made it a bit more obvious what needs to be done now in CVS:

 2007-01-23  Tim-Philipp Müller  <tim at centricular dot net>

       * src/Makefile.am:
         Make clearer which Makefile variables need renaming if the plugin
         name is changes (#399746) (pretty it is not, but it's the content
         that counts, right?)