Piping between Wine and Linux C application?

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
Tester
Level 2
Level 2
Posts: 10
Joined: Thu Mar 05, 2015 4:50 pm

Piping between Wine and Linux C application?

Post by Tester »

Edit:
Wine 1.7.38
Ubuntu LTS 14.04

Example of an error trying to include the Linux OpenNI2-FreenectDriver code under Wine (modifying the Wine makefile to point to the libraries required):

"error: #error OpenNI Platform Abstraction Layer - Win32 - Microsoft Visual Studio Version below 2003 (7.0) are not supported!"

So I have a native Windows dependent C application running under Wine that's communicating with external hardware, and we also have another piece of Linux C application that's communicating with a sensor (using OpenNI2-FreenectDriver), and we want to send data in between these two applications. Would doing a pipe work (FIFO or any other IPC such as socket)? Or is there a smarter way to go about it?

e.g. if we link to Linux C specific FIFO C headers and Linux implementations into the Wine-Windows code.

Running both programs under wine together would be another layer of unnecessary complexity and would potentially create more problems since there are alot of Windows vs Linux specific sensor issues (OpenNI, OpenCV, etc).

Thanks
cheako
Level 2
Level 2
Posts: 19
Joined: Sun Apr 26, 2015 11:33 pm

Re: Piping between Wine and Linux C application?

Post by cheako »

The simplest is to use networking address 127.0.0.1.

Regular files are often used for this, ala named pipe(mkfifo) these are *about* the same.

Wine applications should be able to access all of the Linux system calls. A good solution is to role your own builtin dll.
Locked