Among other things this is required for certain API calls now used in
recent libserialport versions (probably will be required for various
other sigrok-related projects later as well).
Uwe Hermann [Fri, 4 Apr 2014 18:51:45 +0000 (20:51 +0200)]
sigrok-cross-mingw: Update for a more recent MXE.
Newer MXE versions (see www.mxe.cc) have a different directory layout
and naming. The triplet "i686-pc-mingw32" is now "i686-pc-mingw32.static",
various path names now have a ".static" suffix, and the environment variable
"PKG_CONFIG_PATH_i686_pc_mingw32" is now called
"PKG_CONFIG_PATH_i686_pc_mingw32_static".
Uwe Hermann [Fri, 4 Apr 2014 18:24:52 +0000 (20:24 +0200)]
sigrok-cross-mingw: Drop MSI Python installer, ship only libs/modules.
Until now we used to include the official Python MSI Windows installer
in the installers for our frontends (sigrok-cli and PulseView), and it
was run during the installation of the sigrok frontend. Python was also
hardcoded to be installed into c:\python32.
Change this to only ship python32.dll and python32.zip now, which are
simply copied into the install location of the frontend (e.g.
"c:\Program Files (x86)\sigrok\PulseView". The python32.zip file
contains a few DLLs and libs, and all Python stdlib modules.
This has various advantages:
- There are no longer issues if a user has other Python versions
installed on the same OS (e.g. a different Python 3 version and/or
Python 2.x versions). The sigrok frontends will always use _only_ the
local Python from their install dir and ignore any others.
- We (or rather the Python MSI installer) no longer create any registry
entries, potentially change the PATH env. variable, change file
associations, add Python to the Windows "list of installed software",
create a Start Menu entry for Python, or do any other things that affect
the system as a whole. After an uninstall of the respective sigrok
frontend no traces of (our local) Python will be left on the system.
- We no longer need to hardcode any path for the Python install. The
required files will always be installed whereever the sigrok frontend
is installed, no matter wheter it's on c:\ or any other drive.
- The installation time is reduced (we no longer need to run the
official MSI installer) and the size of our NSIS installers is also
reduced quite a bit (python32.dll + python32.zip are a lot smaller
than the full Python MSI installer).
- Frontend load times might even be reduced a bit, since Python will now
only scan for modules in the two locations we provide (the
python32.zip file and the decoders/ subdirectory).
Add srd_decodersdir.patch which replaces the (now obsolete) patches
pulseview_decodersdir.patch and sigrok_cli_decodersdir.patch.
Uwe Hermann [Thu, 30 Jan 2014 21:20:12 +0000 (22:20 +0100)]
sigrok-cross-mingw: Drop -DENABLE_COTIRE=y.
This seems to cause issues on some Ubuntu versions (likely due to an
older cmake version, but we didn't investigate much). We're just
dropping the Cotire use in this script to avoid the problems, since it
is a fully optional thing (only affects compile performance) anyway.
Uwe Hermann [Mon, 13 Jan 2014 23:55:28 +0000 (00:55 +0100)]
sigrok-cross-linux: Add file for simple Linux (cross-)compiles.
This script can be adjusted to build the sigrok components for various
Linux-based targets via various cross-toolchains.
Per default it will do native builds though, i.e. it can also be used
just as a simple "I don't want to type that much" script to clone,
build, and install (e.g. in $HOME/sr) all sigrok components in one go.
Uwe Hermann [Sun, 5 Jan 2014 09:51:06 +0000 (10:51 +0100)]
sigrok-cross-mingw: Also ship zadig.exe and zadig_xp.exe.
This is a helper tool for installing libusb-win32 or WinUSB drivers on
Windows, which is a requirement for USB devices to be recognized by
libsigrok (libusb actually) on Windows.
Marcus Comstedt [Wed, 28 Aug 2013 12:19:44 +0000 (14:19 +0200)]
sigrok-cross-android: Set PKG_CONFIG_LIBDIR globally
PKG_CONFIG_LIBDIR overrides the global directory for .pc files.
This way, no globally installed package files for the build system
will be picked up. Also, PKG_CONFIG_PATH is unset to prevent any
local build system packages from being found. Only the packages built
by the script itself should be found.
Uwe Hermann [Mon, 5 Aug 2013 12:44:53 +0000 (14:44 +0200)]
Move/rename firmware extractor tools.
Since sigrok-util will be released as tarball with the usual build
system at some point, and the tools will be installed in /usr/bin by
most distros, the tools need to have unique names as to not conflict
with other things in /usr/bin. We use a common 'sigrok-fwextract-' prefix
for all current and future firmware extractor tools to keep the
names consistent and unique.
Drop the .py suffix from the executables, since the implementation
language doesn't matter and is generally not encoded in the filename
in things installed in /usr/bin.
Later on, every tool will also get a manpage, of course.