Skip to main content

[LINUX] Hiding the source file and Linking the objects file

In order to prepare the exercise for students in RTEMS on Raspberry Pi, I dig into Makefile (which is auto generated by automake) this week.
(The way to build up the example in RTEMS on Raspberry Pi : here)

The perspective of exercise is to let the students adopt our library to design a simpler real-time application.
However, I want to hide the source code of library, but let the framework of makefile still work well.
That is, we have to exclude the data dependency from the auto generated makefile.

Assume we already compile the essential object as the library and place it at Source code directory, i.e., "...../rtems-gpio/testsuites/samples/SEMAPHORE_TEST".
If we open Build directory, i.e., "build-rtems-rpi-gpio/arm-rtems4.11/c/raspberrypi/testsuites/samples/SEMAPHORE_TEST", we can find a Makefile that is generated by using automake with Makefile.am in Source code directory.

As the typical rule in Makefile framework, all the dependencies of object will be denoted like this:

Pibrella.o:\
 ../../../../../../../rtems-gpio/c/src/../../testsuites/samples/SEMAPHORE_TEST/Pibrella.c \
../config.h \
... so on.

However, we cannot directly find this kind of information from Makefile in Build directory.

Lets trace the file by bottom-up (This example is called SEMAPHORE_TEST):

... 
SEMAPHORE_TEST$(EXEEXT): $(SEMAPHORE_TEST_OBJECTS) $(SEMAPHORE_TEST_DEPENDENCIES)
        @rm -f GPIO_Pibrella$(EXEEXT)
        $(make-exe) 
...

You can find the same rule here and the dependent files are defined with the object.

...
am_SEMAPHORE_TEST_OBJECTS = init.$(OBJEXT) Pibrella.$(OBJEXT) \
        tasks.$(OBJEXT)
SEMAPHORE_TEST_OBJECTS = $(am_SEMAPHORE_TEST_OBJECTS)

Here OBJEXT is ".o".
...
include ./$(DEPDIR)/Pibrella.Po
include ./$(DEPDIR)/init.Po
include ./$(DEPDIR)/tasks.Po
...
Behind the implicit keyword, .SUFFIXES:, we can find the include line as include ./$(DEPDIR)/Pibrella.Po, which is used to reveal the dependency of Pibrella.o generated by automake.
DEPDIR here is an invisible directory called .desp in Source code directory.

By marking this line, we can exclude the checking of dependent file and keep the assumed object file with the source codes of example.
Therefore, we reach our perspective.

------------BTW, one of my friends ask me that how to enable math library in RTEMS compilation:
For example, it is a question like this:
https://lists.rtems.org/pipermail/users/2006-March/014215.html

Ad-hoc way is to open Makefile.am in the same folder:
LINK_LIBS = $(NXT_LDLIBS)
add -lm at the end of line.
LINK_LIBS = $(NXT_LDLIBS) -lm

Comments

Post a Comment

Popular posts from this blog

RSB+RTEMS 5/6 with QEMU-SMP (ARM realview_pbx_a9_qemu as example)

Since I got a request regarding this blog  written in 2016, summarizing again the complete flow with the latest version of RTEMS could be a good idea. Prepare a suitable workspace according to the adopted operating system on your host ( https://docs.rtems.org/branches/master/user/hosts/index.html ):  sudo apt-get build-dep build-essential gcc-defaults g++ gdb git unzip pax bison flex texinfo unzip python3-dev libpython-dev libncurses5-dev zlib1g-dev Checkout RSB and build: git clone git://git.rtems.org/rtems-source-builder.git rsb change directory to rsb/rtems/ and type ../source-builder/sb-set-builder --prefix=<the path you like to store the built toolchains> <the name of bsp> For example, to use QEMU, I need toolchains for ARM, so: ../source-builder/sb-set-builder --prefix=/home/kh.chen/respository/build/. 6/rtems-arm This will take a while. Please ensure your connection is reliable. Add the built folder into your PATH. For example, you can add one line in ~/.bas...
Post a Comment
Read more

[Gem5] Full system Simulation with Official Kernel

I follow the youtube provided by Gem5 to get the inspiration. (http://gem5.org/Running_gem5#Full_System_.28FS.29_Mode) I download the file here: http://www.gem5.org/dist/current/arm/ with http://www.gem5.org/dist/current/arm/aarch-system-20170616.tar.xz Then Set up M5_PATH as the place I extract the files: "/home/khchen/full_system_images/" If the setting is correct, assigning the disk-image will finish the rest of setting for dtb and kernel specifications. So far I can only use this img (aarch32-ubuntu-natty-headless.img) as my disk-image to run up to the login interface of the ubuntu: build/ARM/gem5.opt configs/example/fs.py --disk-image=/home/khchen/full_system_images/disks/aarch32-ubuntu-natty-headless.img With the other imgs, for example like "aarch64-ubuntu-trusty-headless.img", I think the kernel and the dtb should be given manually, because it will automatically load something with aarch32 prefix which doesn't make sense: info: kernel ...
Post a Comment
Read more

Efficient Computation of Deadline-Miss Probability and Potential Pitfalls

Fortunately, I will attend the DATE 2019 conference to present my work. The title of my work is: Efficient Computation of Deadline-Miss Probability and Potential Pitfalls This work is regarding the approximation of Deadline-Miss probability for soft real-time systems. The abstract is as the following: In soft real-time systems, rare deadline misses are often tolerable by the applications. Towards this, probabilistic arguments and analyses are applicable to the timing analyses of this class of systems, as demonstrated in many existing researches. Convolution-based analyses allow to derive tight deadline-miss probabilities, but suffer from a high time complexity. Among the analytical approaches, which result in a significantly faster runtime than the convolution-based approaches, the Chernoff bounds provide the tightest results. In this paper, we show that calculating the deadline-miss probability using Chernoff bounds can be solved by considering an equivalent convex optimization ...
Post a Comment
Read more