Skip to main content

Posts

Showing posts from May, 2018

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 ...

[RTEMS/QEMU] RTEMS 5 with QEMU-SMP

Let me first show what I can get: *** BEGIN OF TEST HELLO WORLD *** *** TEST VERSION: 5.0.0.b771cb48a61c6094da114d064df7d6b1daa01953 *** TEST STATE: EXPECTED-PASS *** TEST BUILD: RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP *** TEST TOOLS: 7.3.0 20180125 (RTEMS 5, RSB 10d3aaf467aee6ec6b463cca04ab873e1c18a5dc-modified, Newlib 3.0.0) Hello World *** END OF TEST HELLO WORLD *** The configuration I used is as follows: ../rtems-kuan/configure --target=arm-rtems5 --enable-rtemsbsp=realview_pbx_a9_qemu_smp --enable-smp --enable-tests=yes --prefix=$HOME/development/rtems/5 qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -kernel hello.exe -smp 4