Opened 10 years ago
Closed 10 years ago
#45731 closed update (fixed)
faust-devel, faust2-devel, faustlive-devel: update to latest git source
Reported by: | agraef (Albert Graef) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch maintainer | Cc: | |
Port: | faust-devel faust2-devel faustlive-devel |
Description
Latest bugfixes from upstream, including improvements in the JSON and Qt GUI support. Also, FaustLive now builds with Qt5 (looks nicer).
Attachments (3)
Change History (8)
Changed 10 years ago by agraef (Albert Graef)
Attachment: | faust-devel-Portfile.diff added |
---|
Changed 10 years ago by agraef (Albert Graef)
Attachment: | faust2-devel-Portfile.diff added |
---|
comment:1 Changed 10 years ago by larryv (Lawrence Velázquez)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Changed 10 years ago by agraef (Albert Graef)
Attachment: | faustlive-devel-Portfile.diff added |
---|
Updated Portfile with Qt5 variant
comment:3 follow-up: 4 Changed 10 years ago by agraef (Albert Graef)
Ok, I committed a fix upstream and updated the Portfile to make that work. New Portfile diff attached. This builds against Qt4 again, or against Qt5 if the qt5 variant is selected. Is that the proper way to do it?
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
I usually add two variants, conflicting with one another, and make one the default.
Updated faust-devel in r127839.
comment:5 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Updated faust2-devel and faustlive-devel in r127843.
Note: See
TracTickets for help on using
tickets.
Replying to aggraef@…:
I wouldn't do this just yet. qt5-mac builds on fewer systems than qt4-mac. And qt4-mac and qt5-mac cannot currently be installed and active simultaneously (#44193) so forcing Qt5 here will prevent faustlive users from using any other ports that use Qt4. We could offer variants to let the user choose Qt4 or Qt5. In that case I would keep Qt4 as the default.