On Thursday, 4 February 2021 17:52:16 PST Paper Chalice wrote:
> Thanks for your reply,
> homebrew installs software into /usr/local/Cellar/software_name/version
> then symlink the content in bin, lib, share to /usr/local. If someone
> installs qt@6 through homebrew and want to install additional
Thanks for your reply,
homebrew installs software into /usr/local/Cellar/software_name/version then
symlink the content in bin, lib, share to /usr/local.
If someone installs qt@6 through homebrew and want to install additional
libraries, e.g. qt3d, qmake will not find the qt3d, because qmake
fi
On Thursday, 4 February 2021 01:56:36 PST Paper Chalice wrote:
> Hi developers,
> I tried to write homebrew formula for qt6 and met a problem. qmake will
> resolve QT_INSTALL_PREFIX to the /usr/local/Cellar/qt/6.0.1, which is not
> friendly to other qt related formulae. I tried to add a patch but I
> On 3 Feb 2021, at 20:14, Joerg Bornemann wrote:
>> But why not get rid of the gap in the first place, ie instead of having a
>> gap between
>>> - final dependency update sha1s are fixed, full update round started
>>> - 6.1 branch is created
>> What stops us from simply creating the branch in th
Hi developers,
I tried to write homebrew formula for qt6 and met a problem. qmake will resolve
QT_INSTALL_PREFIX to the /usr/local/Cellar/qt/6.0.1, which is not friendly to
other qt related formulae. I tried to add a patch but I don't know the side
effects, in homebrew's build env formula have n