Xcode Source Editor Extension Questions

Question

Created Jun ’16

Replies 3

Boosts 0

Views 1.3k

Participants 2

Hi All:

I've created a new source editor extension and did the sudo /usr/libexec/xpc... as described in the Xcode beta release notes.

I have 5 commands in the editor.

When I run my extension the new copy of Xcode starts, it presents the open project dialog, I pick a scratch project and when I go to the Editor menu, my extension is greyed out.

I've see the extension show the commands before, it just seems to be grey since I added some code to the extension. It's some old c++ code, so I changed the sourceEditorCommand extension from .m to .mm (had to start somewhere...). I'm wondering about any entitlements that I might not have set. Is there some documentation on what entitlements have to be set when using a source code extension?

Deployment target is 10.11, base SDK 10.12.

My computer is a Mac Pro 2013, Mac OS 10.11.5, Xcode 8 beta.

Any hints as to why the extension is greyed out? Do I have to do the development in 10.12 beta?

Thanks

John

Boost

Answer 1

jeroenfromutrecht OP

Jun ’16

I had the same. I waited, while the greyed-out second Xcode app was presented, with starting the test app until the extension was fully build. Then it turned black. And I had quit and run Xcode once before.

0

Answer 2

IntelJohnny OP

Jun ’16

I think my extension is built completely built (it's not that big - right now)before the grey Xcode is started, but if giving it a bit more time is the solution, I'll try that tonight.

Thanks for your input

John

0

Answer 3

IntelJohnny OP

Jun ’16

That was it. Just a little patience. I waited until I saw 'running... ' in the activity view in the original Xcode and my menu is enabled and selecting a menu item fires off the 'performCommandWithInvokation' message.

Now on to the 'real' work!

Thanks again

John

0