* In the MacPorts environment, Ruby 2.7 is used.
* Updated the build tools for Mac supporting Qt-5.15.2 from MacPorts.
* Updated the Ruby environment for BigSur and Catalina.
* To update the Mac DMG maker to support Big Sur.
* Updated the resource files for Mac DMGs.
* * Updated the build system for Mac
* Catalina env. uses Python 3.8 in MacPorts, Homebrew, and Anaconda3.
* Use Ruby 2.7 in MacPorts.
* Test build for macOS "Big Sur" (11.0) on Intel Mac "Catalina" (10.15.7).
* Updated the build system for macOS, including the future support for Big Sur (11.0)
* Changing indentation to 4 spaces
* squash
* removing more global variables (squash)
* | tee always exits with 0
* parameter is a dictionary now
* Changing default Makefile to HB38 and adding -rbinc2 option for Catalina
* Catalina building...
* macQAT fixed
* run_build_command depends on parameteres dict alone
* Adding options to macbuild/makeDMG4mac.py
In particular, we can now specify a -u (unsafe) option, and
specify the target dmg file with -t target.dmg
This reverts commit fa96f6d352.
Thinking about it, it would be horrible for deployment. Need to rethink this.
Klayout will break once python goes to 3.7 and brew updates it.
- Assuming user installing with brew wants the library link to go to cellar rather than /usr/local/opt/.
- Python gets updated often in brew, and an update could possibly break klayout.
Using brew's qt and python3 formulae
Bonus: I have also added a script that embeds python into bundle, recursively adding dependencies from inside /usr/local/opt. That means that /usr/local/lib folders are not going to be copied. I saw one dependency to /usr/local/lib/gcc from one of numpy's modules, instead of pointing towards /usr/local/opt/gcc/lib/gcc.
Side effects: Renaming Qt5Custom to Qt5Brew
Kazunari Sekigawa
Thomas Ferreira de Lima
Matthias Koefferlein
Kazunari Sekigawa