Bug 107906 - Build Error on linux: gst_plugins_base - error: unknown type name 'GST_XXX_API'
Summary: Build Error on linux: gst_plugins_base - error: unknown type name 'GST_XXX_API'
Status: RESOLVED MOVED
Alias: None
Product: gstreamer
Classification: Unclassified
Component: account (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium major
Assignee: Thomas Vander Stichele
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-11 20:22 UTC by Kim,Tae-Soo
Modified: 2018-09-11 21:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Screen shot of build error. (41.19 KB, image/png)
2018-09-11 20:22 UTC, Kim,Tae-Soo
Details

Description Kim,Tae-Soo 2018-09-11 20:22:18 UTC
Created attachment 141528 [details]
Screen shot of build error.

Dear All.

When I downloaded the latest GStreamer souce code and tried to build.
But build error occured.
I think some files did not include xxx-prelude.h file which defines GST_XXX_API macro. (ex. GST_TAG_API, GST_AUDIO_API, GST_VIDEO_API...)

Is there real issue on the source code, or did I do something wrong?

Would you please check it?

Thank you.
Comment 1 Tim Müller 2018-09-11 21:23:47 UTC
Thanks for the bug report, but the GStreamer project does not track bugs in this bug tracker, it tracks its bugs on bugzilla.gnome.org, see https://gstreamer.freedesktop.org/bugs

Please file a bug there instead. Apologies for the inconvenience.

I think the problem in your case might be that your "common" module is not up to date.

If you are compiling from git, run "git submodule update" and git clean everything and re-run autogen.sh; make

If you have a custom setup or a merged repository or so you may need to include this commit from the common submodule:

commit f0c2dc9aadfa05bb5274c40da750104ecbb88cba
Author: Tim-Philipp Müller <tim@centricular.com>
Date:   Tue Mar 13 00:32:34 2018 +0000

    gst-glib-gen.mak: add foo_gen_decl_include for api decorator define


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.