-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Surge with a fork of VSTGUI #527
Conversation
557ffcb
to
cbe193d
Compare
OK @falkTX I pushed cleaner documentation. Clearly I was too close to it when I wrote it. thanks for looking. Sorry it was so sloppy. Again this was fiddly to do and tricky to describe. |
cbe193d
to
efa5172
Compare
You should document the reasoning. We should have an architecture document that should evolve over time. Now it can just have this documented. Otherwise, sounds good. |
Yeah will copy some of the text I. #515 into the document before I push good idea |
@baconpaul did you see the conversation on the surge-irc chat where Files in question:
|
Not yet; but the problem with using Lato isn't changing the code (tho that's good to know it helps) but is getting the font file loadable on the users machine. That's the work in #214. I'll say the same in slack! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM and makes sense to take this approach 👍 ; hope Steinberg moves reasonably quickly to get fixes merged though
Thanks. As discussed on slack, as well as @jsakkine comment on adding a motivation section to the doc, I'll also add a comment on the steinberg branch strategy |
efa5172
to
b832995
Compare
This diff begins building Surge with a fork of VSTGUI rather than the VSTGUI which ships with the vst3sdk pointer. It accomplishes it by the following: 1. there is a fork of vstgui called `surge-synthesizer/vstgui` with a branch called `surge` which is master + diffs 2. There is a submodule in surge called `vstgui.surge` which points at that branch 3. There are changes to premake to point our vstgui implementation This version points to a surge which integrates three of @sagantech's changes Closes surge-synthesizer#394: Cannot move window after selecting preset Closes surge-synthesizer#396: Diacritical marks in menus Changes for submenu checkmarks on windows Also this diff implements our fork strategy described in surge-synthesizer#515 and closes surge-synthesizer#515 as a result.
b832995
to
12aca83
Compare
OK after review from each of you I"m going to merge this. |
This diff begins building Surge with a fork of VSTGUI rather than the VSTGUI which ships with the vst3sdk pointer. It accomplishes it by the following: 1. there is a fork of vstgui called `surge-synthesizer/vstgui` with a branch called `surge` which is master + diffs 2. There is a submodule in surge called `vstgui.surge` which points at that branch 3. There are changes to premake to point our vstgui implementation This version points to a vstgui which integrates three of @sagantech's changes Closes surge-synthesizer#394: Cannot move window after selecting preset Closes surge-synthesizer#396: Diacritical marks in menus Changes for submenu checkmarks on windows Also this diff implements our fork strategy described in surge-synthesizer#515 and closes surge-synthesizer#515 as a result. Former-commit-id: ce8bc4274c88df2915b9b3abac26078f273959a6 [formerly 7314657] Former-commit-id: 0c72f1c331f2281cbd9de138a495d999c172a39c Former-commit-id: c97dce7fb3bbc8c8d3a44af05e4c7b8022c6fde1
This diff begins building Surge with a fork of VSTGUI rather than the
VSTGUI which ships with the vst3sdk pointer. The rationale is described
in #515 and elsewhere.
It accomplishes it by the following:
surge-synthesizer/vstgui
with a branchcalled
surge
which is master + diffsvstgui.surge
which points at thatbranch
This first version points to a branch which has one and only one
vstgui fix in it; which is submenu checkmarks on windows. But
by building this way we address that problem.