Tim said:
'winCE' to appear in the list of options we would need for a winCE platform directory tree to be built since right now the menu is built from the subdirectories of /platforms. Files in common with win32 could be linked to, copied or simply referred to in the makefile
Adding a suitable WinCEVMMaker subclass is a good starting point and I suspect some other code would be needed. Yoshiki is almost certainly the Man For The Job.
Yes, Tim. It is what I have done and all works ok adding the WinCEVMMaker class by hand after seen how VMMaker is been instantiated... The effect of instantiating a VMMaker instance when I have only put the folder for WinCE, was that the new VMMaker instance created remove the files of directories without any notification and it was difficult to know what is happening because the instance created when opening is VMMaker tool was a Win32VMMaker... (I donĀ“t know if you will understand,... the implicit change of the VMMaker to an instance of a more abstract class without notification is not what I expected to happen).
I have searched the web for months for a winCE porting using VMMaker, but not luck. I have built it now and I think that it is working with basic plugin support (B3D,File,JPEG,BMP,Deflate,Misc,Socket). Now I want to add FFI support, because it was what I need. When completed I plan to make it public; but if anyone is interested, I can send the project sources or put them where you think it is convenient to be found in the future. Now, there is some versiones of WinCE implementations but all made by hand and not included with the Win* platforms as required by people that want to start looking at it.
best, Ale.
----- Original Message ----- From: "Tim Rowledge" tim@sumeru.stanford.edu To: Dean_Swan@Mitel.COM Cc: squeak-dev@lists.squeakfoundation.org Sent: Sunday, October 24, 2004 9:22 PM Subject: Re: Gcc dependencies in VMMaker
Dean said:-
Is there any easy way to get VMMaker to generate C code that doesn't include all the Gcc dependencies that the latest version does? I'm
trying
to build an updated 3.7 VM for WinCE (i.e. my iPaq 2210), and the
current
VMMaker output from 3.7-5989 Full makes MS VC++ quite cranky.
I'm puzzled - there's nothing at all that was deliberately put into VMMaker to support gcc. It should produce as vanilla C as we can manage, though I suspect it does tend a little towards C99 standard and one of my wannadoos is to try making use of the __inline__ pragma sometime soon.
WinCE support is likely to be a bit flaky since (to the best of my knowledge) no support for it has been put in either. Since I don't do any development work on either it relies on others submitting code and I simply don't seem to have any. So far as I can remember Yoshiki has done pretty much all the handling of winCE VMs.
Ale. said:-
One of the problem is related with instantiation of the VMMaker. The #default message returns an instance for building the image in the
host
platform. So, when you open the VMMaker with the menu, all is ok. But IF YOU CHANGE (by hand) the last editbox contents with title "path
to
generated sources", a new VMaker can be instantiated and provably if you named the directory for WinCE platform, the wrong instance will be
created
(aVMMaker instance).
The intent is that when you open a VMMakerTool UI the default of a VMMaker suitable for the platform you're running on is made. If you choose a different platform from the list ('Find platform') a new instance of the actual VMMaker is built to suit the chosen platform and the configuration copied over (just in case you had setup any plugin config etc). Changing the 'Path to generated sources' should most definitely not rebuild the VMMaker instance attached to the VMMakerTool. I've just tried this and that seems to be correctly working. Note that the name for the generated sources directory has nothing to do at all with the platform name or VMMaker subclass. For 'winCE' to appear in the list of options we would need for a winCE platform directory tree to be built since right now the menu is built from the subdirectories of /platforms. Files in common with win32 could be linked to, copied or simply referred to in the makefile
Adding a suitable WinCEVMMaker subclass is a good starting point and I suspect some other code would be needed. Yoshiki is almost certainly the Man For The Job.
tim
Tim Rowledge, tim@sumeru.stanford.edu, http://sumeru.stanford.edu/tim Any programming language is at its best before it is implemented and used.