Re: opencv python bindings

On Wed, Jan 17, 2018 at 12:48 PM, szgyg wrote: > Different packages, python2-cv2 and python3-cv2. > Oh man, I'm such an idiot. I was looking all over for opencv packages, didn't think to look for cv2 packages. In any case, Thanks! Pete -- Problem reports:

opencv python bindings

Hello, uname: CYGWIN_NT-10.0 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin Running on Windows 10. I've installed the opencv(3.2) and libopencv3.2 packages, but those packages apparently didn't contain the python bindings (cv2)? The opencv_version.exe -v indicates that the python2 bindings

using Cygwin (-mno-cygwin) to JNI to a 3rd party DLL

Hello, We have a 3rd party Windows DLL that we want to interface with from Java, obviously using JNI. The 3rd party DLL provides a link lib to link against. It's a pure C interface (no C++). I've used the 3rd party DLL just fine for a while now from MSVC (ver 6), but now we want to call it

Re: using Cygwin (-mno-cygwin) to JNI to a 3rd party DLL

On 5/1/07, Brian Dessent [EMAIL PROTECTED] wrote: You'll have to run this in a debugger to be sure, but I'd start looking at calling convention clashes, i.e. stdcall vs cdecl. This should be a function of the header files and how they declare prototypes. The thing that's odd is that without

Re: GNU make and VPATH problems

Pete Flugstad wrote: So, before I start trying to debug GNU make, has anyone seen anything like this? I'll work on recreating the problem with a simplified setup, so I can post an example here, but I'm hoping someones seen this before. Getting no response, I downloaded the GNU make 3.80-1

GNU make and VPATH problems

Greetings, I just recently started having a problem with GNU make. I believe it's related to VPATH, but I'm not sure. The weird part is that I think it just recently started happening after I ran the cygwin update (which did not update GNU make). I checked the mailing list archvies and I