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 793234 - Building for Android with gstreamer-1.0.mk fails
Building for Android with gstreamer-1.0.mk fails
Status: RESOLVED DUPLICATE of bug 791854
Product: GStreamer
Classification: Platform
Component: cerbero
2.x
Other Windows
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-07 06:58 UTC by StefanS
Modified: 2018-02-07 08:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description StefanS 2018-02-07 06:58:10 UTC 
Building GStreamer 1.12.4 with Android NDK on Windows fails.
Following error message is reported:


-->
GStreamer      : [GEN] => gst-build-armeabi/gstreamer_android.c
Done rm
Done mkdir

Der Befehl "#" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

Done cp

make: *** [genstatic_armeabi] Error 1
make: *** Waiting for unfinished jobs....
<--


The German sentence means, that the "#" command is spelled incorrectly or missing.

I traced this back to following code in gstreamer-1.0.mk:


-->
genstatic_$(TARGET_ARCH_ABI):
	@$(HOST_ECHO) "GStreamer      : [GEN] => $(PRIV_C)"
	@$(call host-mkdir,$(PRIV_B_DIR))
	@# android-studio doesn't seem to like line continuation characters when executing shell commands
	@$(SED_LOCAL) "s/@PLUGINS_DECLARATION@/$(PRIV_P_D)/g" $(PRIV_C_IN) | $(SED_LOCAL) "s/@PLUGINS_REGISTRATION@/$(PRIV_P_R)/g" | $(SED_LOCAL) "s/@G_IO_MODULES_LOAD@/$(PRIV_G_L)/g" | $(SED_LOCAL) "s/@G_IO_MODULES_DECLARE@/$(PRIV_G_R)/g" > $(PRIV_C)
<--


Problem is solved if the "@# android-studio..." line is removed.
Comment 1 Sebastian Dröge (slomo) 2018-02-07 08:38:01 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 791854 ***