Расписание электричек из Бланеса в Барселону: http://www.renfe.com/viajeros/cercanias ... index.html (в качестве пункта отправления указываете Blanes, в качестве пункта назначения - любой вокзал в Барселоне, например Barcelona-Plaça de Catalunya). Электрички, как видите, ходят довольно часто. Время в пути - примерно 1 час 20 минут.
Программы, собранные на Qt требуют множество дополнительных файлов, таких как: Qt5Widgets.dll Qt5Gui.dll Qt5Core.dll libwinpthread-1.dll libstdc++-6.dll libgcc_s_dw2-1.dll icuuc52.dll Это далеко не полный список возможных зависимостей. Как от них избавиться? Нужна статическая сборка Qt. В интернете много разных статей на эту тему, но они мне не понравились по разным причинам. Поэтому я решил написать свою. Протестировано для: Qt 5.3.2, компилятор MinGW 4.8.2 32bit, Windows 7 64bit. Написано на основе qt-project.org/wiki/How-to-build-a-static-Qt-for-Windows-MinGW но без использования Windows PowerShell.
O-profile must be cross-compiled for the platform under test. It requires the following libraries: libintl, libbdf, libliberty (part of binutils) libpopt First you need to compile the binutils (preferrably the same used by your cross compiler) as follows: ./configure –target=arm-linux –host-linux –build=i686 –without-gettext –without-intl –prefix=$SRCBLB/libs make make install You also need to compile gettext (It can be download from one of GNU servers) to be able to compile binutils (even though this was disabled)
Here is what I want to do: I am developing a userspace program which needs to exchange data and signals with a kernel space module which I have written. For transferring data, I am already using ioctl. But I want the kernel module to be able to signal the userspace program whenever new data is ready for it to consume over ioctl. To do this, my userspace program will create a few eventfds in various threads. These threads will wait on these eventfds using select() and whenever the kernel module updates the counts on these eventfds, they will go on to consume the data by requesting for it over ioctl.
Whatever language or client library you're using, you should be able to set the timeout on network socket operations, typically split into a connect timeout, read timeout, and write timeout. However, although you should be able to make these timeouts as small as you want, the connect timeout in particular has an effective maximum value for any given kernel. Beyond this point, higher timeout values you might request will have no effect - connecting will still time out after a shorter time. The reason TCP connects are special is that the establishment of a TCP connection has a special sequence of packets starting with a SYN packet. If no response is received to this initial SYN packet, the kernel needs to retry, which it may have to do a couple of times. All kernels I know of wait an increasing amount of time between sending SYN retries, to avoid flooding slow hosts.