Hi Esteban,
On Mon, Oct 03, 2011 at 11:54:58AM -0300, Esteban Lorenzano wrote:
hi, I'm coming back with this issue (yep... no time last couple of weeks, but this one is a lot better :) I still can not compile FT2Plugin with the last changes, adding:
#bytesPerWord #generateBytesPerWord:on:indent: #baseHeaderSize #generateBaseHeaderSize:on:indent:
..etc...
you know, real problem is that #generateBytesPerWord:on:indent: generates a plain "BytesPerWord"... but BytesPerWord is not defined anywhere... so I assume there is something I'm missing, but I don't know why.
In other things, I'm determined to produce a beta release this week. As far as I know, I just need to solve some minor issues:
- this FT2Plugin issue
I am away and cannot look at this right now, but when I last built a Cog VM to test this I was using the configure / make procedure (not the CMake procedure) and it seemed to be working, but maybe I was confused or maybe there is there is some difference related to the build procedure. Sorry, I am only guessing, and I'll try to look at it again in a couple of days.
- externalize OSProcess (yes... I don?t like to have it as an internal plugin)
I think there was an issue on some of the Mac platforms that required a compiler flag to force the compiler to make global variables visible (for the environment vector, etc). Is that the problem here? I do not have a Mac, but I'll try to help figure this out if I can.
Dave
- a stupid issue with localization strings (just used on open images)
and I don't think anything else :) so... if you help me with this issue... you will make me very happy :D
cheers, Esteban
El 19/09/2011, a las 5:27p.m., David T. Lewis escribi?:
I am away so I cannot look at the code right now, but in the oscog VMMaker you should still have BytesPerWord implemented as a class variable (or pool variable?), and this would be a C macro in the generated code. In the plugin, we use "self bytesPerWord" rather than a reference to the BytesPerWord class variable (because BytesPerWord does not exist in the trunk 32/64 bit code generation).
In VMMaker trunk, "self bytesPerWord" is translated to the C macro "BYTES_PER_WORD". In oscog VMMaker, it is translated to "BytesPerWord" which also happens to be a C macro. This works on both branches of VMMaker.
If this is not working for you, let me know the specific VMMaker and FT2Plugin MCZs that you have loaded, and I will try to reproduce this when I get home (about 8 hours from now).
Dave
On Mon, Sep 19, 2011 at 05:12:56PM -0300, Esteban Lorenzano wrote:
applied... now I have errors on FT2Plugin.c (it calls BytesPerWorld... and it does not exist....) what I'm missing? :( (I'm feeling sooooo dumb today...)
cheers, Esteban
El 19/09/2011, a las 3:50p.m., David T. Lewis escribi?:
On Mon, Sep 19, 2011 at 09:45:25AM -0300, Esteban Lorenzano wrote:
Hi, I'm trying to build freetype plugin with latest version (Freetype-Plugin-dtl.63), and it is not working... and using Igor's version (61) it is working fine... unique change between 61 and 63 is:
bytesPerWord "Answer the size of an object pointer in bytes."
^BytesPerWord
...so... something is wrong with that change... or with my attempts to understand it :P maybe I'm missing some initialization?
Hi Esteban,
You are missing the code generation patch, which is in VMMaker-oscog-dtl.124. This has not yet been merged into the main oscog branch, so you will need to merge it yourself before building the Freetype plugin.
The changes are here: http://lists.squeakfoundation.org/pipermail/vm-dev/2011-September/009328.htm...
And background is in this thread: http://lists.squeakfoundation.org/pipermail/vm-dev/2011-September/009291.htm...
Dave