Alan W. Irwin ir...@beluga.phys.uvic.ca writes:
Note also, my whole argument is based on the assumption that some standard
means already exists for telling compilers running on Wine to #define
__WINE__ at run time. However, if such standard means do not already exist
there is no way I would
On 2010-06-18 11:44+0200 Alexandre Julliard wrote:
Alan W. Irwin ir...@beluga.phys.uvic.ca writes:
Note also, my whole argument is based on the assumption that some standard
means already exists for telling compilers running on Wine to #define
__WINE__ at run time. However, if such standard
On Fri, Jun 18, 2010 at 11:37 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
If what you want is to add workarounds for Wine in your code, then
neither __WINE__ nor the build platform matter. What matters is the
platform your code is currently running on, which should be detected at
On Fri, Jun 18, 2010 at 6:43 PM, Austin English austinengl...@gmail.com wrote:
On Fri, Jun 18, 2010 at 11:37 AM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
If what you want is to add workarounds for Wine in your code, then
neither __WINE__ nor the build platform matter. What matters is the
On 2010-06-18 19:26+0200 Roderick Colenbrander wrote:
On Fri, Jun 18, 2010 at 6:43 PM, Austin English austinengl...@gmail.com wrote:
On Fri, Jun 18, 2010 at 11:37 AM, Alan W. Irwin
Which leads to a Wine newbie question. What is the best way to detect the
Wine
platform at run time?
Doing so
According to some old discussion
(http://www.mail-archive.com/wine-de...@winehq.com/msg15669.html) on
wine-devel it appears that __WINE__ was going to be the macro used to
identify the Wine platform,
However, that doesn't appear to work for Windows native MinGW on wine.
To show this, I attach
On Thu, Jun 17, 2010 at 4:56 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
According to some old discussion
(http://www.mail-archive.com/wine-de...@winehq.com/msg15669.html) on
wine-devel it appears that __WINE__ was going to be the macro used to
identify the Wine platform,
However,
You seems to have made one mistake - it is winegcc, (without space) not wine
gcc. winegcc does define __WINE__ .
--- On Thu, 17/6/10, Alan W. Irwin ir...@beluga.phys.uvic.ca wrote:
According to some old discussion
(http://www.mail-archive.com/wine-de...@winehq.com/msg15669.html)
on
On 2010-06-17 17:13-0400 Mike Kaplinskiy wrote:
On Thu, Jun 17, 2010 at 4:56 PM, Alan W. Irwin
ir...@beluga.phys.uvic.ca wrote:
According to some old discussion
(http://www.mail-archive.com/wine-de...@winehq.com/msg15669.html) on
wine-devel it appears that __WINE__ was going to be the macro
On 2010-06-18 01:23+0100 Hin-Tak Leung wrote:
Alan W. Irwin wrote:
Thus, is there not some standard means that could be used
for wine to tell the various MinGW compilers built on Microsoft Windows but
run under wine to always #define __WINE__?
I am quite sure AJ will object to any such
On 06/17/2010 02:56 PM, Alan W. Irwin wrote:
However, that doesn't appear to work for Windows native MinGW on wine.
Correct. Programs running under Wine should not and are not aware of the
fact they are running on Wine and not the real Windows. This aspect 100%
analogous to a software running
Alan W. Irwin wrote:
Thus, is there not some standard means that could be used
for wine to tell the various MinGW compilers built on Microsoft Windows but
run under wine to always #define __WINE__?
I am quite sure AJ will object to any such things - as far as the various
compilers (and
12 matches
Mail list logo
