From the Xcode 3.2 Release Notes:
You can add your user to the _developer group. Note that there is also a Developer forum.
Standard user accounts are be asked to authorize developer privileges with either an admin or developer
group user and password once per log-in session when debugging or using the performance tools.MacBook Pro, Mac OS X (10.6.4), (and various older stuff keeping dust off the shelves)
There are several ways to add your user to the *Developer Tools* group. You can use System Preferences > Accounts, a utility such as TinkerTool System, or a Terminal command - I haven't used this method, but it is mentioned in several places (for example the Xcode-users mailing list)
sudo dscl . append /Groups/_developer GroupMembership <username>MacBook Pro, Mac OS X (10.6.4), (and various older stuff keeping dust off the shelves)
Currently Being ModeratedNov 20, 2010 10:07 AM (in response to red_menace)I think if appleaka could run "sudo", this wouldn't be a problem
You will have to ask whomever administers your network to add you to that group. As a developer, you really should have admin access to your own machine. That is standard corporate policy at most places, including the very restrictive places that I have worked in.MacBook Pro, Mac OS X (10.6.4), + iPad + MacBook 2007
Currently Being ModeratedNov 20, 2010 10:37 AM (in response to red_menace)sudo dscl . append /Groups/_developer GroupMembership <username>
just to clarigy, when you type in <username> at the end, do you type in "<appleaka>" or "appleaka"?
in other words
sudo dscl . append /Groups/_developer GroupMembership appleaka
sudo dscl . append /Groups/_developer GroupMembership <appleaka>iMac Late 2009, Mac OS X (10.6.4), iMac, iPod Touch 2nd Generation w/ OS 3.1.3, iPod Nano 3rd Generation
Just your user name
... and as etresoft mentioned , you will need administrative access (I use a standard account myself, but am the admin).
sudo dscl . append /Groups/_developer GroupMembership appleakaMacBook Pro, Mac OS X (10.6.4), (and various older stuff keeping dust off the shelves)
ok thank you everyone for your help, but why does Xcode ask for admin access? when you run a terminal script (or as i found any Mac app made in Xcode) are you editing sytem files, that could end up messing up the computer?iMac Late 2009, Mac OS X (10.6.4), iMac, iPod Touch 2nd Generation w/ OS 3.1.3, iPod Nano 3rd Generation
Xcode normally doesn't ask for admin access. I think it is an artifact of how your managed account is setup. I have a similar setup on my work machine. Although I rarely run Xcode, I do get asked for an admin account password every so often. I think the cause is my Juniper VPN, but I'm not sure.MacBook Pro, Mac OS X (10.6.4), + iPad + MacBook 2007
There might be something in the Developer Tools that they are concerned about, although I don't know what it would be - maybe something that runs as root in order to do its thing. I normally run from a standard account, and was asked for admin access for that until I added it to the group.MacBook Pro, Mac OS X (10.6.4), (and various older stuff keeping dust off the shelves)
Currently Being ModeratedJan 27, 2012 12:44 PM (in response to red_menace)
Unfortunately adding over 300 constantly changing users to almost 300 machines isn't an option for me.
Instead of adding users to _lpadmin, I can change /etc/cups/cupsd.conf to give mere mortals the power
to unpause a printer. If there isn't anything that I can change in my image to make it work including file
perms, is there something I can do in Workgroup Manager using an AD group to populate _developer?
Bumping this response as I'm in the same boat. I have an instructor that wants to teach XCode, but it keeps asking for an admin password. My knee jerk reaction is to create an AD group and give them to run Xcode as an admin.
So much easier, and quicker to create an AD group . . . . she teaches in several classrooms and I just don't plain have the time to manually enter 20+ users on all those machines.
Anyone done the above and can live to tell the tale