In the next weeks I will review the book “OpenCV Computer Vision with Python” and I’ll post my opinion here. Let’s dive in the opencv python module 
The Raspberry Pi (RPi in advance) board has become in the last year one of the favourite toys for geeks & programmers. Although it has a reasonable powerful processor, if we have in mind to develop a large project in this little board, the development process should be performed in a (more suitable) workstation and then perform cross compilations to generate binaries for the RPi architecture (ARM). There already exists some available tutorials explaining how to do the cross-compilation and debugging using the Eclipse IDE. However, as most of the readers of this blog know, I don’t like to be tied to the usage of a specific IDE, and I have been using CMake for configuring my software projects for quite a while (and letting anyone using their favourite programming environment to develop). Therefore, in this post I will explain how to do the cross-compilation process with CMake and how to debug the applications in the remote target from our host workstation. Here we go! Leer más…
Configuring big Qt projects with CMake could be sometimes annoying because of the necessity to apply the moc command over those specific header files containing the Qt Q_OBJECT macro. Long time ago the CMake macro qt4_wrap_cpp was introduced to help in the preprocessing of those files and it helps a lot. However, in big projects where we have header files containing Q_OBJECT macro and other ones where the macro is not included we have to specify the first ones in a list of files that will be preprocessed with the qt4_wrap_cpp macro. An Cmake configuration example of what I’m talking about could be:
SET(COMMON_SRC file1.cpp file2.cpp file3.cpp)
SET(COMMON_HDR file1.h file3.h)
SET(COMMON_UIS file1.ui file3.ui)
QT4_WRAP_CPP(COMMON_MOC ${COMMON_HDR})
QT4_WRAP_UI(COMMON_UIS ${COMMON_UIS})
ADD_LIBRARY(project_common ${COMMON_SRC} ${COMMON_MOC} ${COMMON_UIS})
But things could be easier. This afternoon I was watching some of the videos of the Qt Developers day in Berlin 2012 (http://www.cyberhades.com/2012/12/13/videos-del-qt-developers-day-berlin-2012/). Between them, I watched the presentation of Stephen Kelly talking about how to configure Qt projects with CMake in Qt4 and Qt5 (Some interesting new features will come soon for the new release of Qt ^^). In his presentation Stephen mentioned a new feature introduced in CMake 2.8.8 that let us avoid to apply the qt4_wrap_cpp macro over those headers containing Q_OBJECT macro. It’s so simple as setting the CMAKE_AUTOMOC variable to ON. Here you have the new version of the previous code using CMAKE_AUTOMOC feature.
SET(CMAKE_AUTOMOC ON)
...
SET(COMMON_SRC file1.cpp file2.cpp file3.cpp)
SET(COMMON_UIS file1.ui file3.ui)
QT4_WRAP_UI(COMMON_UIS ${COMMON_UIS})
ADD_LIBRARY(project_common ${COMMON_SRC} ${COMMON_UIS})
Two weeks ago, I made a speech in my work about the usage of CMake for configuring C/C++ projects in order to be independent from platforms (Windows, Linux, Mac, QNX, etc) and IDEs/Editors. In this speech I treated general concepts and commands of CMake and also specific cases such us the usage of Qt and cross-compiling. I prepared the slides in my free time I decided to use a Creative Commons licence to share them with some pieces of code too. Be free to share this work in non commercial mode and with acknowledgement to the author.
CMake tutorial by Luis Díaz Más is licensed under a Creative Commons Reconocimiento-NoComercial 3.0 Unported License.
It has been almost two years from the last posts about FreeWRL (post1 & post2). It has rained a lot since then … Now the freewrl project is in its version 1.22.13 and it even has a version for Android and Blackberry. However the documentation of the project shines by its absence. As in older versions, we need to install some packages, but luckily, nowadays is much less messy than in the past. I will simply left the packages you need to install in Ubuntu 12.04 in order to compile successfully the project:
libfreetype6-dev libmozjs185-dev libxaw7-dev libimlib2-dev imagemagick libglew1.6-dev
The rest of the installation process follows the traditional procedure in GNU/Linux tarballs.
Últimos comentarios