Article:		Plug It In, Plug It In
Subject:		Can't build bundle
Date:		2002-10-19 18:56:14
From:		psheldon
Response to: Can't build bundle
You didn't miss what I missed at first reading the log file. I couldn't make either. You saw that .bundle was at the end of the thing it couldn't make, but, from things we entered elsewhere, it should have read ".plugin" in the log file. I looked at targets and saw bundle was still there in target name, but I had done stuff to make it plugin. I quit project builder and then launched it again and found that name had changed. Subsequent compiling didn't produce that "can't make error". I am very curious whether I was able to observe around this target spelling "weakness" and if you will find a similar wierd "fix" or, instead, think even more differently than me. ;-) In build phases frameworks and libraries, I also put in AppKit.framework, in addition to Cocoa.frameworks. This seemed plausible, but wasn't evidentally necessary as it wasn't in Mike's working source. Project builder seemed to quit unexpectedly when I asked it to quit, so I am getting paranoid about saving rather than have it remind me. It can't remember to remind me if it is being surprised by quitting. ;-) A working hypothesis for systems engineers at Apple is saving and quitting must subscribe to the same sort of internal stuff, a module that they got confused in the latest version of project builder. Last night, I thought I would be crazy to write this in a thread, but today, having gotten the victory of finishing the column's whole program bug free, I am not so embarrassed to suggest that someone else might have made a mistake and even guess where to help.

Showing messages 1 through 3 of 3.

• Can't build bundle - fixed - new compile error
  2002-10-20 19:23:36  johnts [View]
  
  
  It turns out, my error was I had the wrong target set when I created the new Copy Files section - it was trying to copy itself...I changed that and that compiled.
  
  However (I still haven't done the second part of the article) I'm getting a compile warning:
  AImageView.m: In function `-[IAImageView validateScrollers]':
  IAImageView.m:34: warning: initialization from incompatible pointer type
  
  At this line in the validateScrollers: method:
  
  NSScrollView *scrollView = [[self superview] superview];
  
  ?????
• ran through article again with my own BlackAndWhite plugin
  2002-10-21 14:45:05  psheldon [View]
  
  
  Took about 1 and 1/2 hours this last time around. Things do get faster once you've learned to make decisions especially pruning one's understanding search space.
  
  That was heartening. It meant I could study a column after going through the struggle and not have to struggle so hard. It is important to review fundamentals and getting the confidence that I didn't have to struggle so hard as the first time was like a liberation.
  
  I think I had to add to Build Phases Frameworks & Libraries something beyond the column :
  AppKit.Framework.
  
  But, Mike didn't have to add that in his project, so I must have done something else. It is hard to keep track of what I did right, even after recapitulating most everything.
  
  At one point copyfiles was on the wrong target and the right one for a long path recursion that log got confused about. I don't recall doing that mistake again.
• Can't build bundle - fixed - new compile error
  2002-10-21 09:57:57  psheldon [View]
  
  
  I too had the wrong target set at one time. It led to a deeper and deeper pathname to the plugin. Every once in awhile I got pathname too long. I started getting desperate and deleted from the build folder in addition to cleaing from PB. Then that error message would disappear for awhile until the file got too deep.
  
  I don't know whether that was associated with the target not renaming itself. I think it was the PB restart that insured the renaming from bundle to plugin.
  
  I too got IAImageView.m:34: warning: initialization from incompatible pointer type but didn't know what to do and got my version working even with the warning, so left understanding this alone.
  
  So, that single warning is not enough to let you know if and why your program is not working.
  
  If you rebuild without a clean all warnings go away and you forget that you ever had them.
  
  ;-)
  
  You must ask yourself "Does my program work?" and not assume the warning means that you have still dones something wrong.
  
  Does your program work now?