Mooseyard MYCrypto → 0.3

Comments and changes to this ticket

• 

  snej April 14th, 2009 @ 02:56 PM

  • State changed from “new” to “open”

  That's kind of weird! Hmm...

  OK, here's my guess: maybe Xcode's IDE understands the "~" in the path you specified, but GCC itself doesn't. That would explain what you're getting.

  Try changing the path in the Xcode prefs to "/Users/joel/Development/MYUtilities" (or whatever ~ expands to.) Let me know if that resolves the problem.

• You flagged this item as spam.
  

  Joel Norvell April 14th, 2009 @ 03:48 PM

  Thanks, Jens. Expanding the path solved the first problem!

  And the second problem is that I didn't have Doxygen on my system.

  I have just installed it in my Applications folder (and rebooted), but I'm still having this problem:

  Building target “MYCrypto” of project “MYCrypto” with configuration “Debug” — (1 error)

      cd /Users/joel/Development/MYCrypto
  /bin/sh -c /Users/joel/Development/MYCrypto/build/MYCrypto.build/Debug/MYCrypto.build/Script-27EAF0C60F8BD4ED0091AF95.sh
  
  

  doxygen: Command not found.

      doxygen: Command not found.
      doxygen: Command not found.
  
  

  Build failed (1 error)

  I'm guessing that I either need to launch Doxygen and do something with it or else move it to a different location. I'm looking through the documentation (Apple's and Doxygen's), but if you know what I'm doing wrong, or not doing, I'd very much appreciate being told!

• 

  snej April 14th, 2009 @ 04:03 PM

  Oh, good point — I should move the Doxygen build step to a new optional target, so it won't prevent people from building without it.

  For now you can either (1) Flip open the target in the project tree and delete the Run Script build phase; or (2) Add the 'doxygen' tool to your shell path, with a command something like: sudo ln -s /Applications/Doxygen.app/Contents/Resources/doxygen /usr/bin (customize this according to where you put the Doxygen app, and where you want the tool to go.)

  Isn't it fun being the first guinea-pig? ;-)

• You flagged this item as spam.
  

  Joel Norvell April 14th, 2009 @ 04:53 PM

  It builds now :-)

  Thanks once more Jens!

  I'm glad to be the first guinea-pig, as long as you're willing to put up with my lack of experience ;-)

  I had to the delete the Run Script build phase though.

  I tried:

  sudo ln -s /Applications/Doxygen.app/Contents/Resources/doxygen /usr/bin

  and that created some strange new build error!

  (I didn't have a good idea of where to destination was supposed to be on my machine so I tried /usr/bin)

  Do you know what command would undo the "ln -s ..." to remove the "clutter" I created? I tried crawling around my file system with "cd" but couldn't find the directory /usr/bin

  I guess it's time to dig out my old copy of Kernighan and Pike!

• 

  snej April 14th, 2009 @ 06:53 PM

  • Milestone set to “0.3”
  • State changed from “open” to “resolved”

  I'm glad it built! I've updated the documentation now, and pushed a new revision of the project file that skips Doxygen if it's not installed.

  To remove the symlink you can just run:

  sudo rm /usr/bin/doxygen

  You must have a /usr/bin directory if you've got the developer tools installed ... it's where a lot of really core tools like 'gcc' and 'make' live.