Re: [self-interest] xcode problems installing Klein
- Adam Spitz wrote:
> I'm not sure what to tell you about the .xcodeproj file. I don't know much aboutThat is what I expected. Perhaps it is a matter of changing some setting
> Mac OS "bundles." On my machine (a Powerbook running Mac OS 10.4.7), when
> I download the Klein distribution from the website and double-click it to unzip it,
> I can find the klein_C_code.xcodeproj file and it shows up correctly (as a single
> bundle, not a directory).
in the uncompression tool? The Mac (a G5 iMac) is at home so I will have
to look into this later.
> Alex suggested that the problem might have something to do with differentI thought you guys might have been using Xcode 3.0 already - I doubt
> versions of Xcode. We've been using Xcode 2.3. I don't know whether that's
> likely to make a difference or not.
there would be any real difference between 2.0 and 2.3. My problem was
very likely to have been in the uncompression stage.
> Is your Macintosh PowerPC-based or Intel-based? I'd be happy to send you myThanks! Though as you mentioned below, I probably don't actually need
> kleinDebugServer executable, but I've only got a PowerPC version.
it. But it might be nice to have in case I do want to run stuff in the
future, so first I will try to fix that bundle/folder thing. If that
doesn't work then it would be great to get the pre-compiled debug server
for the PowerPC.
> In any case, though, you shouldn't need the debug server just to browseI got dumped into the VM# prompt and didn't try restarting the scheduler
> through the sources. At what point during the file-in process do you run
> into errors? (What does the console output look like?)
(and then the desktop) to see what would happen. I'll have to run it
again to see what the errors were.
> The postFileIn for the vmKits module tries to run Klein's automated testIt looked like all the files had been read in and there were lots and
> suite (which requires the debug server to be working), but by the time
> you get to that point, all the Klein source code has been filed in. Assuming
> you've gotten to that point, you should be able to browse through the
> sources (maybe after closing the existing Self world and opening a new one)
> with no trouble.
lots of tests sending their output to the console, each one related to a
PowerPC instruction (I think - it has been a looong time since I looked
at that processor's instruction set). I will try "prompt start" and
"desktop go" (just looked these up ;-) if I get another crash.
One thing I am interested in is comparing Klein with the sources for
Exupery, which is a bytecode-to-x86 compiler written in Squeak
Smalltalk. The goals are rather different (the focus for Exupery is good
code generation at the cost of compilation speed) so I want to see what
effect, if any, that had on the program structure.
- Jecel Assumpcao Jr schrieb:
> > Alex suggested that the problem might have something to do with differentThere is a difference. Xcode 2.0 uses the .xcode extension / bundle
> > versions of Xcode. We've been using Xcode 2.3. I don't know whether that's
> > likely to make a difference or not.
> I thought you guys might have been using Xcode 3.0 already - I doubt
> there would be any real difference between 2.0 and 2.3. My problem was
> very likely to have been in the uncompression stage.
format and Xcode 2.2 switched to the .xcodeproj extension / bundle
C. Ramakrishnan cramakrishnan@...
Illposed Software http://www.illposed.com
- Chandrasekhar Ramakrishnan wrote:
> > I thought you guys might have been using Xcode 3.0 already - I doubtThanks for the tip! This made me think that perhaps the bundle thing is
> > there would be any real difference between 2.0 and 2.3. My problem was
> > very likely to have been in the uncompression stage.
> There is a difference. Xcode 2.0 uses the .xcode extension / bundle
> format and Xcode 2.2 switched to the .xcodeproj extension / bundle
stored in the same database that associates file types with
applications, so I just tried renaming the folder and though Mac OS X
wasn't too happy about letting me do that the result was that the folder
was automatically transformed into what looks like a file. Clicking on
that calls Xcode which complains that this was created in a newer
version, Making it open this anyway caused a few errors but otherwise
It turns out that the error I got when loading Klein happens even if the
debug server is running. Something about "no 'sourceHand' in nil" with a
long stack trace and finally a primitive failure where _SetTimer (or
similar - sorry that I didn't make a copy of the error log) got a large
integer as an argument. Just typing "prompt start" was enough to have
the GUI running again, and I was able to build a complete image and run