PB Errors

[Josh]

I just got the newest version and when I try to compiler it tells me that the build failed and to look at the log. The log gives nothing helpful, but a compiled version of the new Hooptie appears anyway so I can still work on it, but anyone know how I can get it to quit giving me build errors?

[OneSadCookie]

What does the build log say?

[Pazolli]

Do you mean you downloaded the Milestone Disk Image (just released) or the CVS source code? Either way I've now moved to using PB2.0 which could well be the source of your problems. Otherwise my question is the same as OSC's (what does the build log say exactly).

I previously hoped you would be able to just open the PB2.0 project file (named "Hooptie.pbproj") and convert it to PB1.0 without trouble, but that might not be the case. Anyway if you're using "Hooptie-old.pbproj" my advice is to try that conversion mentioned above. If that doesn't work, probably the difference that is causing the problem is that "Hooptie-old.pbproj" contains "wav" files in PB's project list (under "Resources - Sounds" I think) instead of "aiff" files (the "wav" files having been deleted and replaced with "aiff" files recently to improve performance and remove bugs on Jaguar). I suspect that would be what is causing the error.

Mark.

[Josh]

Originally posted by Pazolli
Do you mean you downloaded the Milestone Disk Image (just released) or the CVS source code?I downloaded it from CVS.Otherwise my question is the same as OSC's (what does the build log say exactly).It says all of the normal things but then when it gets to linking it gives this:

...skipped <LinkWithFrameworksAndLibraries>Hooptie.app for lack of
<DeriveAndCompileSources>Hooptie.app

...skipped <RezResourceManageFiles>Hooptie.app for lack of
<LinkWithFrameworksAndLibraries>Hooptie.app

...skipped <Hooptie>Hooptie.app for lack of
<CopyResources>
It then tells me that the build has failed and to check to build log.I previously hoped you would be able to just open the PB2.0 project file (named "Hooptie.pbproj") and convert it to PB1.0 without trouble, but that might not be the case. Anyway if you're using "Hooptie-old.pbproj" my advice is to try that conversion mentioned above.The "Hooptie.pbproj" gives me build errors about not finding things like _PrerollMovie and the like.If that doesn't work, probably the difference that is causing the problem is that "Hooptie-old.pbproj" contains "wav" files in PB's project list (under "Resources - Sounds" I think) instead of "aiff" files (the "wav" files having been deleted and replaced with "aiff" files recently to improve performance and remove bugs on Jaguar). I suspect that would be what is causing the error.No, that was one of the first things I checked and the errors don't correspond.

[OneSadCookie]

...skipped <LinkWithFrameworksAndLibraries>Hooptie.app for lack of
<DeriveAndCompileSources>Hooptie.app

...skipped <RezResourceManageFiles>Hooptie.app for lack of
<LinkWithFrameworksAndLibraries>Hooptie.app

...skipped <Hooptie>Hooptie.app for lack of
<CopyResources>


The actual error is before that point. Can you post the entire log?

The "Hooptie.pbproj" gives me build errors about not finding things like _PrerollMovie and the like.

Does the project link against QuickTime.framework?

[Josh]

Originally posted by Pazolli
If that doesn't work, probably the difference that is causing the problem is that "Hooptie-old.pbproj" contains "wav" files in PB's project list (under "Resources - Sounds" I think) instead of "aiff" files (the "wav" files having been deleted and replaced with "aiff" files recently to improve performance and remove bugs on Jaguar). I suspect that would be what is causing the error.Grr... my newness (or stupidity) to PB comes back to bite me. Problem: in order to get the Hooptie code to my Mac OS X computer I must put it on a floppy. In order to get it to fit on the floppy, I deleted the music. But PB was still trying to find the music, hence the error. Thanks to Mark and OSC for sticking with me through my stupidity :(

[Pazolli]

No problem. Good luck with your improvements and sorry I haven't been more responsive (re: your e-mails) this week as I've been rather busy. Unfortunately my non-Hooptie work will probably be quite heavy for the next month and a bit, but don't interpret that to mean I'm not interested in Hooptie (or your work). Also thanks for spotting that grammatical mistake and the clickable screen is something people have been asking for for awhile, so it's great to hear that is implemented. On an unrelated note (for everyone) I've also decided to tighten Hooptie's memory consumption which (with luck) will spell increased performance on less powerful machines.*

Cheers,
Mark Pazolli

* You know how Hooptie sometimes causes the Hard Disk to click over during play, well that could be due to a range of things but often virtual memory is the reason hence by improving memory usage one can improve performance.