Remove command-line options of build_mac_dep.sh
See original GitHub issue/README.md
tells us to install non-brew dependencies with the following command
scripts/build_mac_dep.sh ranges_v3 googletest fmt double_conversion folly re2
However, it seems easier to remove the command-line options.
scripts/build_mac_dep.sh
We can make build_mac_dep.sh
to call the install_xxx
functions for a fixed set of tools.
Does this make sense?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Linux Rm Command Help and Examples - Computer Hope
rm removes each file specified on the command line. By default, it does not remove directories. When rm is executed with the -r...
Read more >Building from the Command Line with Xcode FAQ
Xcode includes all of the command-line tools. If it is installed on your system, remove it to uninstall the command-line tools.
Read more >DISM Operating System uninstall Command-Line Options
Set the number of days that a user has to uninstall a Windows upgrade. /Get-OSUninstallWindow. Run this command against an online image to...
Read more >Linux / UNIX delete a file using rm command - nixCraft
To remove or delete a file or directory in Linux, FreeBSD, Solaris, macOS, or Unix-like operating systems, use the rm command or unlink...
Read more >How to Remove (Delete) a File or Directory in Linux
How do I delete a file in Linux using the command line option? How can I remove a Linux directory? Deleting files and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I actually had the same experience, and I too trimmed the list to avoid reinstalling all the prior packages each time.
Sounds very good for me. Thanks @wenleix !
I am thinking that this might not be very urgent at this moment indeed. It seems more urgently, we’d need to set up CI to verify that these installation and building steps work on Mac and Linux VMs. Does this make sense?