Hi Ken,
On Feb 3 16:50, Ken Brown wrote:
On 2/3/2015 10:27 AM, Corinna Vinschen wrote:
On Feb 3 08:04, Ken Brown wrote:
On 2/3/2015 6:33 AM, Corinna Vinschen wrote:
Hey guys,
On Jan 28 21:23, Corinna Vinschen wrote:
https://cygwin.com/setup-test-x86.exe
Corinna Vinschen writes:
Try this:
Works a treat, please install.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
On Feb 3 22:27, Corinna Vinschen wrote:
On Feb 3 22:04, Corinna Vinschen wrote:
On Feb 3 21:37, Achim Gratz wrote:
I'm not sure we're talking about the same thing. I've recently added
code to print an error message along with the parameter usage when a
wrong option or other
David Stacey writes:
On 04/02/15 20:41, Achim Gratz wrote:
If this sounds like a good idea to everybody else I'd remove the current
test package for 5.18.4 on 32bit and replace it with another test
package for 5.14.4, likely in about two weeks. Comments or suggestions?
Do you expect the XS
Bill promised several time to update cmake, but it seems clear to
me that is has no the time to take care of it.
It will be better to officially declare the package orphan so another
volunteer can take it.
Happy to adopt it. I have some builds of latest 3.1.1 sitting around
that I can send
As I said in another thread I intend to skip directly to version 5.22
shortly after it becomes available in May (assuming the release schedule
is still holds).
While looking into some of the test fails on 5.18.4 I've moved back to
5.14.4 for comparison (the fail turned out to be a combination of
On 2/3/2015 4:17 AM, Corinna Vinschen wrote:
On Feb 2 10:46, Ken Brown wrote:
I've now begun working on the 64-bit build. I found a few minor things I
had to change, and the build was pretty far along, when I apparently hit a
gcc bug:
[...]
Oh, that's too bad. I hope somebody from the gcc
On 04/02/15 20:41, Achim Gratz wrote:
If this sounds like a good idea to everybody else I'd remove the current
test package for 5.18.4 on 32bit and replace it with another test
package for 5.14.4, likely in about two weeks. Comments or suggestions?
Do you expect the XS modules built against
Given our past experience[1][2] in working with upstream, anyone who
maintains a working cmake is going to have to carry patches long-term,
if not permanently.
[1] http://www.cmake.org/Bug/view.php?id=10122
[2] http://www.cmake.org/pipermail/cmake/2010-October/040353.html and
thread
Yes, those
By “adopt,” you are offering to participate in the package
contribution system, which involves a bit more than just putting
tarballs in a shared Dropbox folder:
https://cygwin.com/setup.html
I'm aware, thanks, I already maintain 4 other packages. I'm putting
these up for review of the
Obviously the patches to the modules won't affect the build of cmake
itself, but they do affect the building of other packages using cmake.
These patches were all added over years of testing and usage, and are
required for a useful cmake package.
Sure. Were the reasons for them ever written
On Wed, 2015-02-04 at 12:45 -0800, Tony Kelman wrote:
Bill promised several time to update cmake, but it seems clear to
me that is has no the time to take care of it.
It will be better to officially declare the package orphan so another
volunteer can take it.
Happy to adopt it. I have
Happy to adopt it. I have some builds of latest 3.1.1 sitting around
that I can send to the list later today. Note that I have temporarily
removed all of the patches from cygwin-ports since none of them were
necessary to build, or changed the results of any of cmake's unit
tests. I'll definitely
Dear all,
I would like to package hidapi and propose it for inclusion in
Cygwin. hidapi is a multi-platform library which allows an
application to interface with USB and Bluetooth HID-Class devices on
Windows, Linux, and Mac OS X. hidapi has been
included in many Linux distributions.
My
Corinna Vinschen writes:
I just applied a bigger patch, which not only changed exit, but the way
how the actual LogFile instance gets accessed in general. I removed the
variable theLog entirely and now, rather than
[...]
Please give it a try. For your convenience I created test releases
On Feb 4 12:19, Achim Gratz wrote:
Corinna Vinschen writes:
I just applied a bigger patch, which not only changed exit, but the way
how the actual LogFile instance gets accessed in general. I removed the
variable theLog entirely and now, rather than
[...]
Please give it a try. For
On Feb 4 10:01, Corinna Vinschen wrote:
On Feb 3 22:27, Corinna Vinschen wrote:
On Feb 3 22:04, Corinna Vinschen wrote:
On Feb 3 21:37, Achim Gratz wrote:
I'm not sure we're talking about the same thing. I've recently added
code to print an error message along with the parameter
Hi,
I am starting to find programs with
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
CMake 2.8.10 or higher is required. You are running version 2.8.9
no problem (yet) on 64 bit but on 32bit yes.
2.8.9 package was released 2.5 years ago, and the 64bit version is due
to Yaakov.
On Feb 4, 2015, at 3:40 PM, Tony Kelman t...@kelman.net wrote:
Happy to adopt it.
BASEURL=https://dl.dropboxusercontent.com/u/8244638/cygwin-cmake
By “adopt,” you are offering to participate in the package contribution system,
which involves a bit more than just putting tarballs in a
On Wed, 2015-02-04 at 16:08 -0800, Tony Kelman wrote:
Obviously the patches to the modules won't affect the build of cmake
itself, but they do affect the building of other packages using cmake.
These patches were all added over years of testing and usage, and are
required for a useful
20 matches
Mail list logo
