DSView is a multi-function signal capture and analysis software. Its main function include logic signal capture and measure, digital protocol analysis and debug, analog signal real-time capture and measure, spectrum analysis, etc. DSView is also an open source software based on sigrok project (www.sigrok.org).
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign up------------------------------------------------------------------------------- |
INSTALL |
------------------------------------------------------------------------------- |
Requirements |
------------ |
- git |
- gcc (>= 4.0) |
- g++ |
- make |
- libtool |
- autoconf >= 2.63 |
- automake >= 1.11 |
- cmake >= 2.6 |
- Qt >= 5.0 |
- libtool |
- libglib >= 2.32.0 |
- libzip >= 0.10 |
- libusb-1.0 >= 1.0.16 |
On FreeBSD, this is an integral part of the FreeBSD libc, not an extra package/library. |
This is part of the standard OpenBSD install (not an extra package), apparently. |
- libboost >= 1.42 (including the following libs): |
- libboost-system |
- libboost-thread |
- pkg-config >= 0.22 |
This is part of the standard OpenBSD install (not an extra package), apparently. |
- check >= 0.9.4 (optional, only needed to run unit tests) |
- libfftw3 >= 3.3 |
Building and installing |
----------------------- |
Step1: Get the DSView source code |
$ git clone git://github.com/DreamSourceLab/DSView |
Step2: Installing the requirements: |
please check your respective distro's package manager tool if you use other distros |
Debian/Ubuntu: |
$ sudo apt-get install git-core build-essential cmake autoconf automake libtool pkg-config |
libglib2.0-dev libzip-dev libudev-dev libusb-1.0-0-dev |
python3-dev qt5-default libboost-dev libboost-test-dev libboost-thread-dev libboost-system-dev libboost-filesystem-dev check libfftw3-dev |
Fedora (18, 19): |
$ sudo yum install git gcc g++ make cmake autoconf automake libtool pkgconfig glib2-devel |
libzip-devel libudev-devel libusb1-devel |
python3-devel qt-devel boost-devel check libfftw3-devel |
Arch: |
$ pacman -S base-devel git cmake glib2 libzip libusb check |
python boost qt5 fftw |
Step3: Building |
$ cd libsigrok4DSL |
$ ./autogen.sh |
$ ./configure |
$ make |
$ sudo make install |
$ cd .. |
$ cd libsigrokdecode4DSL |
$ ./autogen.sh |
$ ./configure |
$ make |
$ sudo make install |
$ cd .. |
$ cd DSView |
$ cmake . |
/* |
* If this step fails, |
* make sure that your pkg-config is properly configured |
* to find the libsigrok and libsigrokdecode libraries |
* (It's not by default in Fedora 23). |
* To do this add 'export PKG_CONFIG_PATH='/usr/local/lib/pkgconfig' |
* to your ~/.bashrc and reload it `. ~/.bashrc`. |
*/ |
$ make |
$ sudo make install |
See the following wiki page for more (OS-specific) instructions: |
http://sigrok.org/wiki/Building |
I am a new Ubuntu user, I need to install autotools, when I search on the Internet various ways are given that do ./configure
and stuff.
Please guide me on how to install autoconf, autotools etc on my system. A step by step guidance would be very helpful
Installing from repositories is always prefered unless you need the last version of autotools. In that case you will have to download it manually and install it manually. GNU autotools are three packages: Autoconf, Automake and Libtool. Here are the steps to manually install it:
Autoconf:
Automake:
Libtool:
Most importantlyYou don't need autotools installed to run ./configure
, that it's a key feature of autotools. On the other hand if you are not given the configure script you will need autotools installed to generate it.
Notemake install
will internally call make
. Thus, there is no need in this case of calling make
. Normally, Autotools expect you to call make
without sudo privileges and make install
with sudo. In this case for simplicity I skipped this guideline. It's (or is it?) fairly reasonable to trust there is no malware in the autotools generated Makefile.
Installing autoconf is easy, type in the terminal:
After installing the packages autoconf, automake and libtool, what I did was reconfigure because the error persisted. Then after reconfiguring I was allowed to compile and install without errors.
The justification of why to use /usr/local
and not /usr/local/apache2
I leave you in the next publication