clang: error: no such file or directory: '/App/Vendor/STPrivilegedTask/STPrivilegedTask.m'

[m99coder]

Hi Mat,

first of all: Great Application.

I wanted to build out of current master because the release included in your repository is quite old and probably not containing the last bugfixes. XCode Version 7.2 (7C68) complains about not finding STPrivilegedTask.m. I already tried git submodule update --remote --merge.

Thanks for any advice.
Marco

[LaurentFough]

Getting the same error.

• different actions though: using Cocoapods to add in the Sparkle framework.

Pod is setup and and install properly... error on build, same as mentioned by @m99coder .

[matryer]

I have no idea I’m afraid, it’s working for me.

Maybe try cloning the repo again!?

On 6 Jan 2016, at 10:47, Laurent Fough notifications@github.com wrote:

Getting the same error.

different actions though: using Cocoapods to add in the Sparkle framework.
Pod is setup and and install properly... error on build, same as mentioned by @m99coder https://github.com/m99coder .

—
Reply to this email directly or view it on GitHub #104 (comment).

[m99coder]

All the Vendor folders are empty. How are they filled? Automatically by XCode build?

[matryer]

They're linked repos - see https://github.com/matryer/bitbar/tree/master/App/Vendor

Try this:

git submodule update --remote --merge

[matryer]

p.s. once we figure this out, we'll add some notes to "Contributing"

[m99coder]

The correct command is git submodule init && git submodule update in the root folder (same folder as .gitmodules file). After this it works like a charm.

Maybe you could also add some notes about where to find the release build. In my case XCode saved it under ~/Library/Developer/XCode/DerivedData/{app-name}/Build/Products/Release/BitBar.app.

[matryer]

We need to make sure this is clear for people wishing to contribute. What’s the best way to do that?

On 6 Jan 2016, at 12:27, Marco Lehmann notifications@github.com wrote:

Closed #104 #104.

—
Reply to this email directly or view it on GitHub #104 (comment).

[m99coder]

I would recommend to add notes to README.md as you suggested. Without git submodule init it won’t work. You have to execute it once. Afterwards git submodule update is fair enough to do the job.

[LaurentFough]

Works (builds fine) for me here.

• with: git submodule init && git submodule update