• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: XCode/xcodebuild problems...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: XCode/xcodebuild problems...


  • Subject: Re: XCode/xcodebuild problems...
  • From: Dix Lorenz <email@hidden>
  • Date: Tue, 10 May 2005 18:55:12 +0200


On 10.05.2005, at 17:57, Chris Espinosa wrote:

On May 10, 2005, at 7:12 AM, Dix Lorenz wrote:

1) I have quite a few warnings turned on and one warning I get is

/usr/include/gcc/darwin/4.0/c++/bits/istream.tcc:60: warning: declaration of '__ct' shadows a member of 'this'
I don't worry about it too much but I think it shouldn't be there...

If the compiler says that a local is shadowing a class member, it is. If you don't want the warning you can use -Wno-shadow.

I understand the warning, but it's not in my code and I want the warnings for my code. I think library code should compile as cleanly as possible with as strict rules as possible. Actually I think every code should do that but especially library code...


2) I have a setting for additional Warnings "-Wmost" in there (I guess it's from the default project setup when I created it, maybe not). I think there should be some interface for it, especially since it affects a lot of the other warnings settings. Setting it seems to override a lot of the others and it's hard to see what warnings are actually switched on.

This is the default in Apple's templates. Any additional settings you make in the target inspector will override the defaults in -Wmost.

I still would like some kind of visual feedback what is actually set by -Wmost, especially when it's pre default in Apples templates. AFAICT it sets a lot of the warnings available in the UI but I don't know exactly which ones. So I switch those on that I want anyway. Most (hah!) are probably not necessary since they are covered by - Wmost but I can't tell and then I start thinking what good is -Wmost good for.


3) Using xcodebuild I get a warning that one XCode-Plugin (J2EEAssistant.pbplugin) "is missing the XCPluginHasUI Info.plist key, it is assumed to have UI and will not be loaded by xcodebuild." I assume it has no effect, especially since I don't use Java in this build but anyway...

This is an older plugin left over from a previous ProjectBuilder/ Xcode installation. You may remove it from /Library/Application Support/Apple/Developer Tools/Plug-Ins if you wish.

Ok, I'll take your word for it, it's gone :-)

4) Another warning using xcodebuild: "(NOTE: project medinet was written by an older version of Xcode (38) -- temporarily upgrading it to version 39 (without modifying project file))". How would I get rid of that? Modifying the project and saving it doesn't work, it was originally created using ProjectBuilder.

This is correct behavior for xcodebuild; it upgrades in memory to build, but doesn't write a new project file. Opening the file in Xcode proper should upgrade it and save it. If this "doesn't work" the project may be locked, please describe what actually happens.

Oh, I got it. It was a remainder from my whole buildscript which actually used some ancient projectfile which I wasn't aware of and hadn't changed in years. Solved.


5) I have 2 projects which build around 10 c++-Tools and are supposed to install it in /dldev/bin (INSTALL_PATH = /dldev/bin). That is a local directory, I created it, I have full permissions. But when it does its linking I sometimes get

/usr/bin/ld: can't write output file: /dldev/bin/adaptdata.osx (Permission denied, errno = 13)

Sometimes it works, sometimes it doesn't, sometimes it stops at another tool... Building from XCode itself is fine. I also tried deleting the dir and creating it new and it worked. One time, then it went back to not working... It used to work without any problems in XCode 1.5 and before...

Odd. Do you have a dual-processor G5, by any chance?

Yes. (I hope that was the right answer...)


One unrelated problem I had forgotten: For one File I get a warning

/usr/bin/libtool: warning same member name (mM3Nucleus-66934396.o) in output file used for input files: /Data/Development/Intermediate Files/cliapps.build/library.build/Objects-normal/ppc/ mM3Nucleus-66934396.o and: /Data/Development/Intermediate Files/ cliapps.build/library.build/Objects-normal/ppc/mM3Nucleus-66934396.o (due to use of basename, truncation, blank padding or duplicate input files)

I don't see any duplicate file or in fact anything where I handle mM3Nucleus.cpp different from all the other .cpp-files...

Thanks,
Dix

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: XCode/xcodebuild problems...
      • From: Chris Espinosa <email@hidden>
    • Re: XCode/xcodebuild problems...
      • From: Scott Tooker <email@hidden>
References: 
 >XCode/xcodebuild problems... (From: Dix Lorenz <email@hidden>)
 >Re: XCode/xcodebuild problems... (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: Codewarrior ->Xcode port
  • Next by Date: re: Local variables not displayed in debugger
  • Previous by thread: Re: XCode/xcodebuild problems...
  • Next by thread: Re: XCode/xcodebuild problems...
  • Index(es):
    • Date
    • Thread