Skip to main content

[LEGONXT] cannot find -llejososek / library missing

From my article last year, I have shown how to build up the source tree for the legacy of NXT source code. With the proper configuration, i.e., set up the path for ARM cross compiler in toolgcc.mak, directly under the sample folder, we should be able to compile the source code and integrate them with the essential kernel objects.

However, someone asks me that why he did some implementation in ecrobot sources and the compiler reports that those new implemented functions are not applicable, i.e., undefined. It is because that all the additional static libraries (those files with extension .a) are required to be compiled in advance before compiling the test suites/samples.

There are some known issues which are solved:
  1. cannot find -llejososek
    This can be solved by compiling the source in folder e.g., "nxtOSEK_proj/c++/src". liblejososek.a will be generated in the parent folder, e.g., "nxtOSEK_proj/c++/"
  2. new implemented functions in ecrobot are undefined
    This can be solved by compiling the corresponding code in ecrobot folder. For example, libnxtway_gs_balancer.a need to be generated by compiling to source in the sub folder nxtway_gs_balancer. libnxtway_gs_balancer.a will be generated in ecrobot folder.
Remark (ref):
.a files are static libraries typically generated by the archive tool. You usually include the header files associated with that static library and then link to the library when you are compiling.
Use command ar can see the content inside. It is usually the correction of .o:
ar tv foo.a

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

[LEGO nxt] Install the Enhanced NXT firmware and Upload the OSEK excutable file with Ubuntu 64bits 14.04 in 2015

This tutorial is referred from Install the Enhanced NXT firmware on NXT . I think this is the critical part to capture the idea from the tutorial for Windows. I have tried many ways to conquer the problem of libnxt3.0, however, I still have some problems on the compilation of fwflash or something else. Though the tutorial for Windows is doable, my preference is to build up everything with Linux environment. Fortunately, I notice that NxTTool in the tutorial for Windows is really powerful. We can handle the firmware updating by using NxTTool in Linux as well! I also refer to this Japanese Blog , which inspire me a lot. As usual, install the required packages: sudo apt-get install libusb-dev:i386 libusb-0.1-4 subversion fpc Please note, here is the case for 64bits user that I change libusb-dev to libusb-dev:i386 comparing to the original tutorial. Instead of using libnxt to do the uploading, here I follow that JP Blog to get the latest version of bricxcc: (The url in blog i...
Post a Comment
Read more

Virtualenv experience or alternatives

Today I have a project which requires several packages on my python. However, due to whatever reason, I have a lot of different versions of python. Before I thought, it was fine to just install and maintain each by each. Maybe it is time to learn how to use virtualenv. (alternatively, you can use module). I first got some quick ideas from here: https://stackoverflow.com/questions/10763440/how-to-install-python3-version-of-package-via-pip-on-ubuntu The magic virtualenv does is that, it copies a series of your python binaries, include, pip, etc., into a folder. The prepared activate script does that, add the export folder into the general variable PATH at its beginning. By doing so, the targeted version of python will be the first target that will be executed. To enable virtualenv, source the position of the above folder/bin/activate To leave the virtualenv, just type deactivate, as it is defined when you load the activate script. For example, I call virtualenv in my home ...
Post a Comment
Read more