I noticed that sq.h is taken from the build dir hierarchy, by the way, so it's not entirely consistent...
I think that's the proper location to grab this file from. The sq.h in the Cross-platform directory probably shouldn't even be there, really.
My understanding is:
src - holds stuff generated by Squeak Cross - holds stuff that all platofrms can use, that wasn't automatically generated unix - holds Unix-specific stuff
Actually, though, src ends up combining all three, the way VMMaker works. This combining behavior seems to be a little tricky to get just right, however....
Or at least I don't understand what is pulled from where, exactly. And I get warnings about duplicate rules in the Makefile.
Could you try deleting platfoms/Cross/SurfacePlugin/SurfacePlugin.c, running configure again, and seeing if the errors go away?
I'm not courageous enough to dive into this autoconf/Makefile stuff to find out why or do something against it, though...
I hear you! autoconf stuff is a mess even at its best!
However, I have attached a new version of sqUnixMemory.c, which removes a few pointer/int cast compiler warnings. Briefly tested with/without mmap enabled.
Awesome, those are annoying! I've uploaded your version now, along with some small changes to sqPlatformSpecific.h I'm sure you made.
-Lex
"Lex Spoon" lex@cc.gatech.edu is widely believed to have written:
My understanding is:
src - holds stuff generated by Squeak Cross - holds stuff that all platofrms can use, that wasn't automatically generated unix - holds Unix-specific stuff From the point of view of VMMaker this is not accurate. The older unix
make stuff used generated/ and unix/ but no Cross/
VMMaker uses -
platforms/ {various platform names}/ vm/ plugins/ {assorted plugins supported by this platform} misc/ {makefiles, resources, help files etc} Cross/ vm/ plugins/ {generic plugin code such as FilePlugin.h}
and the src/ directory gets copies of all the files needed for the chosen platform with the chosen configuration.
Actually, though, src ends up combining all three, the way VMMaker works. This combining behavior seems to be a little tricky to get just right, however....
It was indeed which is why I suggest living with the way VMMaker does it for now. No need to make life more difficult.
tim
squeak-dev@lists.squeakfoundation.org