Re: [fpc-devel] wince port
From: Michael Van Canneyt [EMAIL PROTECTED] unidef.inc updated 100% starting func.inc where can i upload wince-api.zip files ? (ftp.freepascal.org/pub/contrib read only) You can send them to me or any of the core developers. It is better to put these files to proper place in rtl\wince in svn. Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] wince port
Yury Sidorov wrote: From: Michael Van Canneyt [EMAIL PROTECTED] unidef.inc updated 100% starting func.inc where can i upload wince-api.zip files ? (ftp.freepascal.org/pub/contrib read only) You can send them to me or any of the core developers. It is better to put these files to proper place in rtl\wince in svn. Send them to me, I'll add them. ___ fpc-devel maillist - [EMAIL PROTECTED] http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] wince port
hi, unidef.inc updated 100% starting func.inc where can i upload wince-api.zip files ? (ftp.freepascal.org/pub/contrib read only) regards ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] wince port
On Sat, 20 Aug 2005, Oro06 wrote: hi, unidef.inc updated 100% starting func.inc where can i upload wince-api.zip files ? (ftp.freepascal.org/pub/contrib read only) You can send them to me or any of the core developers. Michael. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port docs at wiki
Yury Sidorov wrote: 2. Since H2PAS dont eat MS headers the easiest way to port is to use win32 Windows unit and remove all functions which are missing in WinCE. The following list of WinCE functions can be used as reference: http://www.rainer-keuchel.de/wince/dllexports/ipaq-coredll.txt First of all there are almost no functions with A suffix and they must be removed. Also some functions exists as wrappers (SetEvent,ResetEvent). Some of them already implemented in system.pp You can start this task. Currently nobody do it. If you will start it, please write about that at wiki and specify your contacts. IMO an important question is if wince and win32 should share the windows unit or not. Does MS have common headers? ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port docs at wiki
From: Florian Klaempfl [EMAIL PROTECTED] Yury Sidorov wrote: 2. Since H2PAS dont eat MS headers the easiest way to port is to use win32 Windows unit and remove all functions which are missing in WinCE. The following list of WinCE functions can be used as reference: http://www.rainer-keuchel.de/wince/dllexports/ipaq-coredll.txt First of all there are almost no functions with A suffix and they must be removed. Also some functions exists as wrappers (SetEvent,ResetEvent). Some of them already implemented in system.pp You can start this task. Currently nobody do it. If you will start it, please write about that at wiki and specify your contacts. IMO an important question is if wince and win32 should share the windows unit or not. Does MS have common headers? The Windows unit must not be shared between win32 and wince. 1. There are separate MS headers for WinCE. 2. win32 Windows unit is generated from GNU Windows headers and it will break any modifications were made in Windows unit to support wince. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port windows.h
1°)actual (wince 4.2) windows.h need at :
windef.h, types.h, winbase.h, wingdi.h, winuser.h, winreg.h, shellapi.h,
ole2.h, imm.h, tchar.h, excpt.h, strsafe.h
actual window.pp (from fpc 2.1.X) look at :
base.inc, errors.inc, defines.inc, struct.inc, messages.inc, ascfun.inc,
unifun.inc, unidef.inc, ascdef.inc, func.inc, redef.inc
considering that :
- many blocks are common, just organized differently (many wince
declarations i just seek in existing win32 code was already there but
in the wrong dir !)
- windows.pp organisation is clearer
- it will be easier to maintain having in the same file, same kind of
code (even for different targets but wince is also 32bits, it's very
close to win32)
- there will also the win64 port question
i propose :
a- move existing win32 files windows.pp + base.inc+errors.inc,
defines.inc, struct.inc, messages.inc, ascfun.inc, unifun.inc,
unidef.inc, ascdef.inc, func.inc, redef.inc
to rtl\win dir
b-add the following defines in every .inc file
in the interface defined block and also in the implementation block
put here all common blocks
{$ifdef WIN32}
at first, put here all existing code, then copy/paste to the common
block according to wince headers
{$endif} //WIN32
{$ifdef WINCE}
put here all wince only code
{$endif} //WINCE
Any comment ?
2°) a type ULONG_PTR is defined in rtl\win\sysosh.inc
with right define depending on 64 or 32 bits
i saw this type only for wince plateform
could it be replaced by PULONG
and ULONG definition added there ?
there are heavily used by windows
but defined with cardinal type.
regards
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port windows.h
Oro06 wrote:
1°)actual (wince 4.2) windows.h need at :
windef.h, types.h, winbase.h, wingdi.h, winuser.h, winreg.h, shellapi.h,
ole2.h, imm.h, tchar.h, excpt.h, strsafe.h
actual window.pp (from fpc 2.1.X) look at :
base.inc, errors.inc, defines.inc, struct.inc, messages.inc, ascfun.inc,
unifun.inc, unidef.inc, ascdef.inc, func.inc, redef.inc
considering that :
- many blocks are common, just organized differently (many wince
declarations i just seek in existing win32 code was already there but
in the wrong dir !)
- windows.pp organisation is clearer
- it will be easier to maintain having in the same file, same kind of
code (even for different targets but wince is also 32bits, it's very
close to win32)
- there will also the win64 port question
i propose :
a- move existing win32 files windows.pp + base.inc+errors.inc,
defines.inc, struct.inc, messages.inc, ascfun.inc, unifun.inc,
unidef.inc, ascdef.inc, func.inc, redef.inc
to rtl\win dir
b-add the following defines in every .inc file
in the interface defined block and also in the implementation block
put here all common blocks
{$ifdef WIN32}
at first, put here all existing code, then copy/paste to the common
block according to wince headers
{$endif} //WIN32
{$ifdef WINCE}
put here all wince only code
{$endif} //WINCE
Any comment ?
As Yury said, MS doesn't share the headers either so I think it's better
to keep them completely independend.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] WinCE port docs at wiki
Hi, The latest info about WinCE port can be found here: http://www.freepascal.org/wiki/index.php/WinCE_port Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
Hi, I reached significant waypoint in WinCE port. I have Hello world application running on WinCE. :) Here are some notes: Official binutils seems to be buggy for WinCE target. I used binutils from Pocket GCC port and they work fine. procedure fpc_cpuinit for ARM performs illegal instruction (rfs r0) on WinCE. A question why this init is needed and is it needed at WinCE? rfs r0 and r0,r0,#0xffe0 orr r0,r0,#0x0002 wfs r0 Currently I excluded this code for WinCE using ifdefs. Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
Yury Sidorov wrote: Hi, I reached significant waypoint in WinCE port. I have Hello world application running on WinCE. :) GJ :) Hope, you'll contribute the patches soon ;) Here are some notes: Official binutils seems to be buggy for WinCE target. I used binutils from Pocket GCC port and they work fine. procedure fpc_cpuinit for ARM performs illegal instruction (rfs r0) on WinCE. A question why this init is needed and is it needed at WinCE? rfs r0 and r0,r0,#0xffe0 orr r0,r0,#0x0002 wfs r0 It turns floating point exceptions on. Currently I excluded this code for WinCE using ifdefs. It doesn't hurt much but you won't get floating point exceptions then. Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
Yury Sidorov wrote: One more question. I created 2 files t_wince.pas and i_wince.pas for WinCE target. But now I see that it will be better to add WinCE support to t_win.pas and i_win.pas files. Is it ok to do that? Yes. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
[fpc-devel] WinCE port
Hello, I started WinCE port. Any help is appreciated. Currently not much is done. I added added new (empty) target wince to compiler and built crosscompiler for arm with wince target. I have some questions: 1. What is simplest way to add wince target to makefiles? The only way I see is to edit all makefile.fpc files and add wince to them. 2. I need fakertl stuff to start. 3. Any knowledge of how to implement export,import,linker stuff for wince target? 4. Port of windows unit for WinCE? Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
Yury Sidorov wrote: Hello, I started WinCE port. Any help is appreciated. Currently not much is done. I added added new (empty) target wince to compiler and built crosscompiler for arm with wince target. I have some questions: 1. What is simplest way to add wince target to makefiles? The only way I see is to edit all makefile.fpc files and add wince to them. What do you mean with all? Only the top level make files should really need extra effort. For the other Makefiles it's enough with a fpcmake of 2.1.1 svn branch to regenerate them. 2. I need fakertl stuff to start. Well, I'am not sure how close wince to win32 is. Maybe you can start with the win32 system unit? 3. Any knowledge of how to implement export,import,linker stuff for wince target? No. Probably the same as win32 does. Playing with the gnu c/binutils for wince would be a good starting point. 4. Port of windows unit for WinCE? No idea how much it from win32 differs. Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
From: Florian Klaempfl [EMAIL PROTECTED] 1. What is simplest way to add wince target to makefiles? The only way I see is to edit all makefile.fpc files and add wince to them. What do you mean with all? Only the top level make files should really need extra effort. For the other Makefiles it's enough with a fpcmake of 2.1.1 svn branch to regenerate them. I do not know much about fpcmake, but as I see there is makefile.fpc file in each directory. fpcmake creates makefile files based on makefile.fpc files. Which makefile.fpc files should be changed to add new target os? 2. I need fakertl stuff to start. Well, I'am not sure how close wince to win32 is. Maybe you can start with the win32 system unit? Yes, I hope actual system unit for WinCE will be based in win32 system unit. But first of all I need fpc to create working WinCE executables, so I need fake (empty) rtl to test it. Yury Sidorov. ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
Re: [fpc-devel] WinCE port
Yury Sidorov wrote: From: Florian Klaempfl [EMAIL PROTECTED] 1. What is simplest way to add wince target to makefiles? The only way I see is to edit all makefile.fpc files and add wince to them. What do you mean with all? Only the top level make files should really need extra effort. For the other Makefiles it's enough with a fpcmake of 2.1.1 svn branch to regenerate them. I do not know much about fpcmake, but as I see there is makefile.fpc file in each directory. fpcmake creates makefile files based on makefile.fpc files. Which makefile.fpc files should be changed to add new target os? I think do get basic things rolling you don't need to change one but create a new one in rtl/wince 2. I need fakertl stuff to start. Well, I'am not sure how close wince to win32 is. Maybe you can start with the win32 system unit? Yes, I hope actual system unit for WinCE will be based in win32 system unit. But first of all I need fpc to create working WinCE executables, so I need fake (empty) rtl to test it. Which tool chain do you plan to use? Using the fakertl is more hazzle than starting with a real system unit :) ___ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
