office-gobmx/android/CustomTarget_sdremote.mk

# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*-
#
# This file is part of the LibreOffice project.
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.

$(eval $(call gb_CustomTarget_CustomTarget,android/sdremote))

sdremote_DIR := $(call gb_CustomTarget_get_workdir,android/sdremote)

$(call gb_CustomTarget_get_target,android/sdremote) : $(sdremote_DIR)/done

$(sdremote_DIR)/done :
	$(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),MAK,1)
	cd $(SRCDIR)/android/sdremote && $(MAKE) clean && $(MAKE) all
	mkdir -p $(SRCDIR)/instsetoo_native/$(INPATH)/bin
	cp $(SRCDIR)/android/sdremote/bin/ImpressRemote-debug.apk $(SRCDIR)/instsetoo_native/$(INPATH)/bin

# vim: set noet sw=4 ts=4:
Add the android module to gbuild Just build the sdremote app for now. Note that this is a pure Java app with no dependencies on (native) code (or Java code, for that matter) from rest of LO. Probably should drop the separate android/sdremote/Makfile and just do what it does in android/CustomTarget_sdremote.mk instead. Adding other Android apps (well, the LibreOffice4Android one likely) to gbuild will require more complexity as they bundle native code, and thus should depend on other modules first having been built. If one wants to go really fancy, one could of course depend on the specific libraries (and other files) being bundled. Let's see... Change-Id: If10761479f348c4993eec40b7f8346edb77f0e0d 2012-08-21 05:52:05 -05:00			`# -- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t --`
			`#`
			`# This file is part of the LibreOffice project.`
			`#`
			`# This Source Code Form is subject to the terms of the Mozilla Public`
			`# License, v. 2.0. If a copy of the MPL was not distributed with this`
			`# file, You can obtain one at http://mozilla.org/MPL/2.0/.`

			`$(eval $(call gb_CustomTarget_CustomTarget,android/sdremote))`

			`sdremote_DIR := $(call gb_CustomTarget_get_workdir,android/sdremote)`

			`$(call gb_CustomTarget_get_target,android/sdremote) : $(sdremote_DIR)/done`

flock is not portable, so use different approach Change-Id: I4a864ddd3681101c8c5d0943d2761ac85bf4161f 2012-08-22 06:49:13 -05:00			`$(sdremote_DIR)/done :`
Add the android module to gbuild Just build the sdremote app for now. Note that this is a pure Java app with no dependencies on (native) code (or Java code, for that matter) from rest of LO. Probably should drop the separate android/sdremote/Makfile and just do what it does in android/CustomTarget_sdremote.mk instead. Adding other Android apps (well, the LibreOffice4Android one likely) to gbuild will require more complexity as they bundle native code, and thus should depend on other modules first having been built. If one wants to go really fancy, one could of course depend on the specific libraries (and other files) being bundled. Let's see... Change-Id: If10761479f348c4993eec40b7f8346edb77f0e0d 2012-08-21 05:52:05 -05:00			`$(call gb_Output_announce,$(subst $(WORKDIR)/,,$@),$(true),MAK,1)`
flock is not portable, so use different approach Change-Id: I4a864ddd3681101c8c5d0943d2761ac85bf4161f 2012-08-22 06:49:13 -05:00			`cd $(SRCDIR)/android/sdremote && $(MAKE) clean && $(MAKE) all`
Clean first for reliability. Copy the apk so push_nightlies.sh finds it Change-Id: Ie14754deb796cc2a03e48b04b31983ddd26968cb 2012-08-21 07:44:54 -05:00			`mkdir -p $(SRCDIR)/instsetoo_native/$(INPATH)/bin`
			`cp $(SRCDIR)/android/sdremote/bin/ImpressRemote-debug.apk $(SRCDIR)/instsetoo_native/$(INPATH)/bin`
Add the android module to gbuild Just build the sdremote app for now. Note that this is a pure Java app with no dependencies on (native) code (or Java code, for that matter) from rest of LO. Probably should drop the separate android/sdremote/Makfile and just do what it does in android/CustomTarget_sdremote.mk instead. Adding other Android apps (well, the LibreOffice4Android one likely) to gbuild will require more complexity as they bundle native code, and thus should depend on other modules first having been built. If one wants to go really fancy, one could of course depend on the specific libraries (and other files) being bundled. Let's see... Change-Id: If10761479f348c4993eec40b7f8346edb77f0e0d 2012-08-21 05:52:05 -05:00
			`# vim: set noet sw=4 ts=4:`