Hise with Git

[ustk]

@sawer I think @d-healey (and many others) are using git from the terminal. I much prefer using gitHub Desktop.
It can do everything you'll generally need, it's easier, faster, and give a nice visual feedback over the commits
Though I understand people that are used to command lines prefer not to switch... I myself use the terminal when I (rarely) need to perform advanced stuff

[Sawer]

@ustk Alright. Yeah the last bit of the video explains how to do everything on GitHub as well, which is pretty handy by the way.
Thanks for replying, really appreciate.

[Dan Korneff]

I'm enjoying the ease of use from SourceTree here.

[Sawer]

@dustbro Uhm thanks for this!

[Sawer]

Well, I've managed to start from scratch and clone the latest Hise version.
I'm trying to open it on Projucer but it tells me its to date.
Should I have the latest Juce before building Hise?

[d.healey]

@sawer said in Hise with Git:

Should I have the latest Juce before building Hise?

No, use the version that comes with the HISE source code. Just ignore the warning.

[Sawer]

@d-healey Thanks. About to build now.

[Sawer]

@sawer

That's why I'm always afraid to build new version ahaha.
Every time I get errors
Any idea on this?

[Sawer]

Thought I needed to put the Juce:: to every point object but its not working.
Any Idea please?

[d.healey]

@sawer Did you checkout the Develop branch?

[Sawer]

@d-healey nope, just clone Hise , placed the sdk in the tools folder and opened it in Projucer. But it's error upon error.

[d.healey]

@sawer said in Hise with Git:

nope, just clone Hise

Then you're building the master branch.

[Sawer]

@d-healey
No, its not. I was sure to select the develop branch.

[d.healey]

@sawer Re-read this thread and rewatch my video. You're building the master branch.

[d.healey]

@ustk said in Hise with Git:

If at the first time you haven't used git, it will be easier to delete the directory and clone
You don't clone "develop", you clone the repository. Then you checkout the branch you need (at this time it is develop)

[Sawer]

@d-healey My bad. Haven't paid attention enough. Thanks, will try again

[Sawer]

Alright. Followed the instructions, I'm still facing the same errors

[d.healey]

@sawer Did you do a fresh clone for this build attempt or is this the same clone as before? If it's the same did you clean the build directory before recompiling?

[Sawer]

@d-healey made everything from scratch:

1. Clone folder
2. Checkout to develop branch
3. placing sdk's
4. Open project with Projucer
5. Saved and opened in IDE

[d.healey]

@sawer Maybe this will help

https://forum.hise.audio/topic/2479/build-fail-semantics-reference-to-point-is-ambiguous/16
https://forum.hise.audio/topic/4425/develop-branch-build-status/186
https://forum.hise.audio/topic/4853/macos-big-sur-xcode-compile-semantic-fail-errors