2013-03-28, 15:38
(2013-03-20, 22:30)mm_half3 Wrote: Maybe using the xcodebuild command line in the readme is not setting things up the same as with the xcode gui. Given your post saying the check is to look in Makefile.include in the xbmc src dir, checked that file and the CFLAGS variable does have -D_DEBUG in it. That explains why the Make command is trying to create the image from the XBMC.app in the Debug directory. But my build did not create the debug directory, maybe because I wanted the release version and used the line in section 4.2 of the readme that has a -configuration Release option in it. Not sure why the CFLAGS in Makefile.include has -D_DEBUG in it, unless it defaults to that, and the xcodebuild -configuration option over rides it. You did mention build/Release and build/Debug should both be there and as soft-links, my build directory only has Release and it is not a link (soft or hard) to anything (checked the inodes). build/Release hast he XBMC.app directory in it.
The original Makefile will work if I create a soft link for build/Debug to build/Release. Is the -configuration Release line in xcodebuild supposed to set that up?
Thanks for the advices only needed to do git clean -xfd, delete the xbmc depends folder and run my script without sudo. Thanks again.
I have another question, i do my custom build of xbmc because i like to have vda decoder enabled but i have a problem with a "Bottom & Left(Right on my case) Edge pixels flickering"(another topic on the forum) that bugs me like hell when hardware acceleration is enabled. If i want to stay up to date i have to git pull all the time and build all over again?