Cannot get project to build about vico HOT 20 CLOSED

Hmm. Which version of XCode are you running?

from vico.

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

from vico.

Version 5.0 (5A1413)

On Sep 30, 2013, at 11:49 PM, Antonio Salazar Cardozo [email protected] wrote:

Hmm. Which version of XCode are you running?

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

from vico.

** 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 [email protected] 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.

from vico.

that is after changing macosx10.7 to macosx

On Oct 1, 2013, at 12:10 PM, William Gloss [email protected] 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 [email protected] 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.

from vico.

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

from vico.

This should now be fixed on master.

from vico.

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.

from vico.

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 [email protected] 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.

from vico.

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?

from vico.

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 [email protected] 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.

from vico.

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.

from vico.

Did the fresh clone make things work?

from vico.

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 [email protected] wrote:

Did the fresh clone make things work?

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

from vico.

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.

from vico.

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 [email protected]:wgloss/vico.git
$ cd vico
$ make run

from vico.

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

On Oct 15, 2013, at 11:20 AM, Antonio Salazar Cardozo [email protected] 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 [email protected]:wgloss/vico.git
$ cd vico
$ make run
—
Reply to this email directly or view it on GitHub.

from vico.

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

from vico.

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

from vico.

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!

from vico.