search

vicoapp / vico

Mac Programmers Text Editor
http://www.vicoapp.com/
658 stars 89 forks source link

Cannot get project to build #60

Closed wgloss closed 11 years ago

wgloss commented 11 years ago

I run make build, this results in the following error statement.

=== BUILD TARGET finish_installation OF PROJECT Sparkle WITH CONFIGURATION Release ===

Check dependencies error: There is no SDK with the name or path '/Users/user/Documents/Code/vico/sparkle/macosx10.7'

\ BUILD FAILED **

The following build commands failed: Check dependencies (1 failure) make: *\ [/Users/user/Documents/Code/vico/build/DEBUG/sparkle/Sparkle.stamp] Error 65

I am on commit commit 1d42c5839c65f7d6da3ed332756c2de3c5676c14

Shadowfiend commented 11 years ago

Hmm. Which version of XCode are you running?

Shadowfiend commented 11 years ago

Either way, try changing macosx10.7 to just macosx and see if that helps.

wgloss commented 11 years ago

Version 5.0 (5A1413)

On Sep 30, 2013, at 11:49 PM, Antonio Salazar Cardozo notifications@github.com wrote:

Hmm. Which version of XCode are you running?

— Reply to this email directly or view it on GitHub.

wgloss commented 11 years ago

\ BUILD FAILED **

The following build commands failed: CompileC /Users/will/Documents/Code/vico/build/DEBUG/sparkle/Sparkle.build/Release/Sparkle.build/Objects-normal/i386/SUUIBasedUpdateDriver.o SUUIBasedUpdateDriver.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler (1 failure) make: *\ [/Users/will/Documents/Code/vico/build/DEBUG/sparkle/Sparkle.stamp] Error 65

On Oct 1, 2013, at 12:36 AM, Antonio Salazar Cardozo notifications@github.com wrote:

Either way, try changing macosx10.7 to just macosx and see if that helps.

— Reply to this email directly or view it on GitHub.

wgloss commented 11 years ago

that is after changing macosx10.7 to macosx

On Oct 1, 2013, at 12:10 PM, William Gloss william.gloss@gmail.com wrote:

\ BUILD FAILED **

The following build commands failed: CompileC /Users/will/Documents/Code/vico/build/DEBUG/sparkle/Sparkle.build/Release/Sparkle.build/Objects-normal/i386/SUUIBasedUpdateDriver.o SUUIBasedUpdateDriver.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler (1 failure) make: *\ [/Users/will/Documents/Code/vico/build/DEBUG/sparkle/Sparkle.stamp] Error 65

On Oct 1, 2013, at 12:36 AM, Antonio Salazar Cardozo notifications@github.com wrote:

Either way, try changing macosx10.7 to just macosx and see if that helps.

— Reply to this email directly or view it on GitHub.

Shadowfiend commented 11 years ago

Huh. That's descriptive O.o I'll see what happens if I try to do a clean build on XCode 5.

Shadowfiend commented 11 years ago

This should now be fixed on master.

Shadowfiend commented 11 years ago

Let me know if you're still having issues—the easiest thing to do will be reclone the directory, though you can also pull and then rm build/DEBUG/gitmodules.stamp and run make again.

wgloss commented 11 years ago

git submodule update --init --recursive -- . fatal: reference is not a tree: 4cb64383813785f57b3bc7056a603840ea5fd83b Unable to checkout '4cb64383813785f57b3bc7056a603840ea5fd83b' in submodule path 'sparkle' make: *\ [/Users/will/Documents/Code/vico/build/DEBUG/gitmodules.stamp] Error 1

On Oct 2, 2013, at 9:15 PM, Antonio Salazar Cardozo notifications@github.com wrote:

Let me know if you're still having issues—the easiest thing to do will be reclone the directory, though you can also pull and then rm build/DEBUG/gitmodules.stamp and run make again.

— Reply to this email directly or view it on GitHub.

Shadowfiend commented 11 years ago

Were you doing a clean clone?

If not, have you already walked through the steps detailed @ http://stackoverflow.com/questions/2155887/git-submodule-head-reference-is-not-a-tree-error to make sure it isn't that your submodule is in a weird state?

wgloss commented 11 years ago

I did not try a clean clone I did a pull merge. I will try a clean clone.

On Oct 7, 2013, at 1:30 PM, Antonio Salazar Cardozo notifications@github.com wrote:

Were you doing a clean clone?

If not, have you already walked through the steps detailed @ http://stackoverflow.com/questions/2155887/git-submodule-head-reference-is-not-a-tree-error to make sure it isn't that your submodule is in a weird state?

— Reply to this email directly or view it on GitHub.

Shadowfiend commented 11 years ago

Cool. This is a pretty heavy change in the submodule (because we're not just switching the commit it points to, but also the remote repository it's pointing to), and I don't know submodules well enough to be sure what's going on heh. Clean clones have worked for me a couple of times, so fingers crossed.

Shadowfiend commented 11 years ago

Did the fresh clone make things work?

wgloss commented 11 years ago

I am working out how to do a clean clone. I don't know how to delete/update my fork on github. On Oct 15, 2013, at 9:33 AM, Antonio Salazar Cardozo notifications@github.com wrote:

Did the fresh clone make things work?

— Reply to this email directly or view it on GitHub.

Shadowfiend commented 11 years ago

Go to Settings, scroll down to the “Danger Zone™”, and you should see the delete button. Then I think you should be able to re-fork.

Shadowfiend commented 11 years ago

An easier solution should be to add the vico repository as a remote, update your local repository, push it, then remove your local copy and re-clone. I think the state that gets messed up is completely local. Something like:

$ git remote add vico git://github.com/vicoapp/vico.git
$ git fetch vico
$ git rebase vico/master
$ git push origin master
$ cd ..
$ rm -r vico
$ git clone git@github.com:wgloss/vico.git
$ cd vico
$ make run
wgloss commented 11 years ago

Thanks, i will try this today and get back to you before tomorrow.

On Oct 15, 2013, at 11:20 AM, Antonio Salazar Cardozo notifications@github.com wrote:

An easier solution should be to add the vico repository as a remote, update your local repository, push it, then remove your local copy and re-clone. I think the state that gets messed up is completely local. Something like:

$ git remote add vico git://github.com/vicoapp/vico.git $ git fetch vico $ git rebase vico/master $ git push origin master $ cd .. $ rm -r vico $ git clone git@github.com:wgloss/vico.git $ cd vico $ make run — Reply to this email directly or view it on GitHub.

Shadowfiend commented 11 years ago

Cool. No rush, just wanting to make sure there's nothing blocking you :)

vgrichina commented 11 years ago

Editing .git/config and removing [submodule "sparkle"] section would also help in such a situation.

Shadowfiend commented 11 years ago

I've done some pretty heavy reworking of the build system to make it build using xcodebuild. I'm going to go ahead and close this issue, since it seems likely that the issue at hand has been resolved, both by the original fixes to the Sparkle submodule and the subsequent changes to the build system. An XCode build bot seems to be successfully building the application, as well.

If you run into additional problems, go ahead and open another issue and we'll see what we can figure out!