In our previous episode, Sven Barth said:
> > On windows, typically binary files are distributed and win64 bins don't work
> > on win32, so win32<>win64.
>
> That is a bit unfair now. Comparing binary only applications to source
> only ones regarding portability.
There is nothing about fairness
Am 17.08.2010 12:43, schrieb Marco van de Voort:
In our previous episode, Sven Barth said:
slight differences from the 32 bit api e.g. regarding exception handling.
The differences are either slight enough to be left to the developer or
be considered CPU dependant (and could thus have been mov
In our previous episode, Sven Barth said:
> > slight differences from the 32 bit api e.g. regarding exception handling.
>
> The differences are either slight enough to be left to the developer or
> be considered CPU dependant (and could thus have been moved into
> $platform-subdirectories like w
Am 17.08.2010 11:43, schrieb Florian Klaempfl:
And don't forget, the win64 api has
slight differences from the 32 bit api e.g. regarding exception handling.
The differences are either slight enough to be left to the developer or
be considered CPU dependant (and could thus have been moved into
> Because I consider Win32 and Win64 as one type of operating system. One
> "OS target". Just as Linux is one operating system for all those
> available platforms.
>
> Maybe it would have been better to name the target "windows" instead of
> "win32" and "win64" from the beginning so there would be
Am 17.08.2010 10:14, schrieb Florian Klaempfl:
Am 17.08.2010 10:11, schrieb Sven Barth:
Am 17.08.2010 10:03, schrieb Marco van de Voort:
In our previous episode, Sven Barth said:
Does anyone know the reason why 64-bit Windows was added as win64
instead of (x86_64-)win32? With Linux it was don
...snip...
4. The JSON html is working now, but the xml one doesn't list anything
in the grid. This might be that I did something wrong, will check
demo2 and try both there.
c; demo2 - demo6
1. "The following package failed to load: lazwebdata" (there are a
lazwebdata.pas and reglazwebdata.pp fi
Am 17.08.2010 09:54, schrieb Sven Barth:
> Am 09.08.2010 22:36, schrieb Jonas Maebe:
>>
>> On 09 Aug 2010, at 22:32, Martin wrote:
>>
>>> Unfortunately it doesn't work. I get the following error:
>>> make.exe all CPU_TARGET=x86_64 FPC=c:\FPC\SVN\ppc386_2_4_0.exe
>>> makefile:199: *** The Mak
Am 17.08.2010 10:11, schrieb Sven Barth:
> Am 17.08.2010 10:03, schrieb Marco van de Voort:
>> In our previous episode, Sven Barth said:
>>>
>>> Does anyone know the reason why 64-bit Windows was added as win64
>>> instead of (x86_64-)win32? With Linux it was done the ${platform}-linux
>>> way as w
Am 17.08.2010 10:03, schrieb Marco van de Voort:
In our previous episode, Sven Barth said:
Does anyone know the reason why 64-bit Windows was added as win64
instead of (x86_64-)win32? With Linux it was done the ${platform}-linux
way as well.
It's afaik microsofts own designation.
If that's
In our previous episode, Sven Barth said:
>
> Does anyone know the reason why 64-bit Windows was added as win64
> instead of (x86_64-)win32? With Linux it was done the ${platform}-linux
> way as well.
It's afaik microsofts own designation.
___
fpc-pas
Am 09.08.2010 22:36, schrieb Jonas Maebe:
On 09 Aug 2010, at 22:32, Martin wrote:
Unfortunately it doesn't work. I get the following error:
make.exe all CPU_TARGET=x86_64 FPC=c:\FPC\SVN\ppc386_2_4_0.exe
makefile:199: *** The Makefile doesn't support target x86_64-win32, please
run fpcm
12 matches
Mail list logo
