Skip to content
This repository has been archived by the owner on Sep 4, 2018. It is now read-only.

Add BBUncrustifyPlugin #17

Merged
merged 1 commit into from
May 2, 2013
Merged

Add BBUncrustifyPlugin #17

merged 1 commit into from
May 2, 2013

Conversation

keith
Copy link
Contributor

@keith keith commented Apr 24, 2013

@supermarin
Copy link
Collaborator

This one isn't ready to be merged yet, as it's install path is different than project name.
We'd need to either parse .xcodeproj or work with .xcplugins.

Or something better :)

@benoitsan
Copy link
Contributor

Do you mean the issue is because the plugin package name is 'UncrustifyPlugin.xcplugin' and the Xcode project is 'BBUncrustifyPlugin-Xcode' ?

@kattrali
Copy link
Contributor

Yep.

@benoitsan
Copy link
Contributor

I made a try. The plugin is correctly installed in the plugins folder with the correct name but is not marked as installed. So I suppose it's the issue you are talking about: you are using the Xcode project name as the key to find the corresponding plugin.

Because an Xcode project can contain one or more targets and because the Xcode project name can be different from the target, an idea would be to add a key in the plugin definition in packages.json to specify the target product name.

It could be something like that:

{
    "name": "BBUncrustifyPlugin",
    "url": "https://github.com/benoitsan/BBUncrustifyPlugin-Xcode",
    "description": "Xcode plugin to uncrustify the source code opened in the editor"
    "product name": "UncrustifyPlugin"
}

Or perhaps better in order to manage the case where there are multiple targets
PS: Supposing that the target name is the only information needed to build the target using /usr/bin/xcodebuild

{
    "name": "BBUncrustifyPlugin",
    "url": "https://github.com/benoitsan/BBUncrustifyPlugin-Xcode",
    "description": "Xcode plugin to uncrustify the source code opened in the editor"
    "target": {
        "name" : "BBUncrustifyPlugin",
        "product name" : "UncrustifyPlugin"
    }
}

@supermarin
Copy link
Collaborator

@benoitsan thanks for sharing that.

The only concern in this approach is that it could make JSON over-complex, and make it a bit harder for people adding packages.

Since this information could be parsed easily, I've added some basic support here: mneorr/Alcatraz@19b7591

For the case of many targets, I guess there should always be a default target which would be used by just running xcodebuild - and that one would be used by Alcatraz.

@supermarin
Copy link
Collaborator

@Keithbsmiley could you please rebase on master and we're ready to 🚢 :shipit:

@keith
Copy link
Contributor Author

keith commented May 2, 2013

Think we're good now

@orta
Copy link
Contributor

orta commented May 2, 2013

woop 🌠

supermarin pushed a commit that referenced this pull request May 2, 2013
@supermarin supermarin merged commit 46243ab into alcatraz:master May 2, 2013
guillaumealgis pushed a commit to guillaumealgis/alcatraz-packages that referenced this pull request Mar 28, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants