Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2010-10

tlhelp32 for WinCE

5 messages · 2 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Sven Barth

Hello together!

As I need to implement tlhelp32 for Windows Mobile I plan to contribute this back to FPC as well.

I'm using jwatlhelp32 from winunits-jedi as a base and now I have two possibilities to proceed:

- extend jwatlhelp32 for WinCE and add it to the units compiled for WinCE (as I don't think that winunits-jedi is compiled for WinCE, I might need to adjust it's Makefile.fpc rather much)
- copy jwatlhelp32 as tlhelp32 to wince-units and adjust it there

Which solution should I chose?

Regards,
Sven

Marco van de Voort
to Sven Barth

In our previous episode, Sven Barth said:

Show quoted text 12 lines
As I need to implement tlhelp32 for Windows Mobile I plan to contribute this back to FPC as well. I'm using jwatlhelp32 from winunits-jedi as a base and now I have two possibilities to proceed: - extend jwatlhelp32 for WinCE and add it to the units compiled for WinCE (as I don't think that winunits-jedi is compiled for WinCE, I might need to adjust it's Makefile.fpc rather much) - copy jwatlhelp32 as tlhelp32 to wince-units and adjust it there Which solution should I chose?

Copy. CE and win32/win64 are afaik separate SDKs. Moreover heavy changes to jwa* would make synchronizing with upstream (which I do once an year if there are significant differences) more difficult.

Sven Barth
to Marco van de Voort
Marco van de Voort wrote 17 lines
In our previous episode, Sven Barth said: > As I need to implement tlhelp32 for Windows Mobile I plan to contribute > this back to FPC as well. > > I'm using jwatlhelp32 from winunits-jedi as a base and now I have two > possibilities to proceed: > > - extend jwatlhelp32 for WinCE and add it to the units compiled for > WinCE (as I don't think that winunits-jedi is compiled for WinCE, I > might need to adjust it's Makefile.fpc rather much) > - copy jwatlhelp32 as tlhelp32 to wince-units and adjust it there > > Which solution should I chose? Copy. CE and win32/win64 are afaik separate SDKs. Moreover heavy changes to jwa* would make synchronizing with upstream (which I do once an year if there are significant differences) more difficult.

That's why I asked ^^

Should I reduce the unit to WinCE related stuff as well? E.g remove $externalsym (and other C++ Builder stuff), remove Ansi types and functions (WinCE provides only the Widestring versions).

Regards,
Sven

Marco van de Voort
to Sven Barth

In our previous episode, Sven Barth said:

Show quoted text 9 lines
> Copy. CE and win32/win64 are afaik separate SDKs. Moreover heavy changes to > jwa* would make synchronizing with upstream (which I do once an year if > there are significant differences) more difficult. That's why I asked ^^ Should I reduce the unit to WinCE related stuff as well? E.g remove $externalsym (and other C++ Builder stuff), remove Ansi types and functions (WinCE provides only the Widestring versions).

In the copy, yes I think you can. It will never pass upstream (in the unlikely case Embarcadero comes up with WinCE anythime soon, they probably will start over again anyway)

Sven Barth
to Marco van de Voort
Marco van de Voort wrote 14 lines
In our previous episode, Sven Barth said: >> Copy. CE and win32/win64 are afaik separate SDKs. Moreover heavy changes to >> jwa* would make synchronizing with upstream (which I do once an year if >> there are significant differences) more difficult. > > That's why I asked ^^ > > Should I reduce the unit to WinCE related stuff as well? E.g remove > $externalsym (and other C++ Builder stuff), remove Ansi types and > functions (WinCE provides only the Widestring versions). In the copy, yes I think you can. It will never pass upstream (in the unlikely case Embarcadero comes up with WinCE anythime soon, they probably will start over again anyway)

When they'll come up with a native compiler for WinCE there will only be a .NET based WinCE to be used :P

I'll report at Mantis once I'm done.

Regards,
Sven