From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5183FFDD.7080707@xenomai.org> Date: Fri, 03 May 2013 20:20:13 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <006201ce45e4$5dc8e4f0$195aaed0$@com> <5183FDA4.2090003@xenomai.org> <037901ce482a$1f10bce0$5d3236a0$@com> In-Reply-To: <037901ce482a$1f10bce0$5d3236a0$@com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] Qt - Xenomai compatibility problem List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: George Pontis Cc: xenomai@xenomai.org On 05/03/2013 08:14 PM, George Pontis wrote: >> -----Original Message----- >> From: Gilles Chanteperdrix [mailto:gilles.chanteperdrix@xenomai.org] >> Sent: Friday, May 03, 2013 11:11 AM >> To: George Pontis >> Cc: xenomai@xenomai.org >> Subject: Re: [Xenomai] Qt - Xenomai compatibility problem >> >> On 04/30/2013 10:50 PM, George Pontis wrote: >> >>> I took a snapshot from git of the current Xenomai code and put it in the hands of the >> software >>> developers. They reported that Qt would not build after patching with Xenomai. The problem >> was that >>> Qt uses "signals" as a keyword, and that conflicts with the function prototype for >> rt_task_notify >>> under xenomai/native: >>> >>> >>> int rt_task_notify(RT_TASK *task, rt_sigset_t signals); >>> >>> >>> Although this is not a Xenomai problem, it might save some users the annoyance if the name >> "signals" >>> could change. >> >> >> Have you tried the obvious fix? >> >> -- >> Gilles. > > > Yes, to us the obvious fix was to edit the function prototype in the include file > and change "signals" to "_signals". And there are no other changes to make to get Xenomai headers included with qt headers? -- Gilles.