Android.mk: include multiple source files using wildcards


In case your Android project consist in a lot of source files you should, normally, add one by one to the LOCAL_SRC_FILES label and this could be a very boring task to complete. Fortunately there is the possibility to make addition of multiple files using wildcards in a very easy way. Let's go to see how to make it.


There is no need of many explanations, just check the Android.mk example below:

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_MODULE := MyProjectName

LOCAL_C_INCLUDES += $(LOCAL_PATH)/SourcesFolder1
LOCAL_C_INCLUDES += $(LOCAL_PATH)/SourcesFolder2

PROJECT_FILES := $(wildcard $(LOCAL_PATH)/SourcesFolder1/*.cpp)
PROJECT_FILES += $(wildcard $(LOCAL_PATH)/SourcesFolder2/*.c)

PROJECT_FILES := $(PROJECT_FILES:$(LOCAL_PATH)/%=%)

LOCAL_SRC_FILES := $(PROJECT_FILES)

include $(BUILD_SHARED_LIBRARY)

As you can see in this example project we have two subfolders (SourcesFolder 1 and 2) containing the project files we want to compile. Wildcards allow to specify the source files extension (.c and .cpp in our example) to add to the project. You can add as many folder you want but you need to be carefully about some points. The first folder to add need to have the assignment command: 

PROJECT_FILES := $(wildcard $(LOCAL_PATH)/SourcesFolder1/*.cpp)

Each new additional folder need to have the command for add to the list:

PROJECT_FILES += $(wildcard $(LOCAL_PATH)/SourcesFolder2/*.c)

Once finished to add all the folders the last instruction line remove the $(LOCAL_PATH)/ prefix from the list. This is very important since without this "patch" the generated files list will not work and the compiler will return an error:

PROJECT_FILES := $(PROJECT_FILES:$(LOCAL_PATH)/%=%)

Here our files list is ready and we can assign to the compiler label:

LOCAL_SRC_FILES := $(PROJECT_FILES)

In case you have some specific source file you want to add "manually" you can change as follow:

LOCAL_SRC_FILES := \
    Source1.c \
    $(PROJECT_FILES)

Now you can start compilation and verify if  the mk file will work as expected.

Comments

  1. cessmestreetFebruary 18, 2016 at 6:42 PM

    Hi. How will you link the files if the sources folders are not inside LOCAL_PATH? Thanks.

    ReplyDelete
  2. FalsinSoftFebruary 18, 2016 at 11:41 PM

    Hi
    As you can see LOCAL_PATH is defined on the top of the makefile and basically point to the current folder where .mk file is called. If you want to use an absolute path like for example /home/username/mypath1/mypath2/myfiles/ you can use this absolute path instead of LOCAL_PATH or, as easy alternative, define a LOCAL_PATH_1 with your secondary path.

    ReplyDelete

Post a Comment

Popular posts from this blog

Access GPIO from Linux user space

Image
GPIO mean "General Purpose Input/Output" and is a special pin present in some chip that can be set as input or output and used to move a signal high or low (in output mode) or to get the signal current status (in input mode). Usually these pin are directly managed by kernel modules but there are an easy way to manage these pins also from user space.
Read more

Android: adb push and read-only file system error

Image
If you want to copy a file from your PC to the connected android device the fasten way is to use adb tool with push command. This command get as params the path of the local file and the remote path to copy in the device. Sometimes, especially if you use adb from Windows or MacOS, and error about read-only file system show up and you can not copy any file.
Read more

Tree in SQL database: The Nested Set Model

Image
Tree structure are very commonly used by all the application who need to manage a large quantity of data. However once have in memory the tree data the application need a way to save them for future use. SQL database can be a good solution but, in this case, we need a way to store data in efficient mode. This post will propose a model called Nested Set.
Read more