Most of the time we get our compilation headers from XCode.app, free software developed by Apple and available via the Apple App Store. cstddef.h and limit.h ) that don’t ship with a fresh copy of MacOS Mojave. The previous steps gave us the Qt 5.5 libraries on which we depend, though we also need some extra C++ libraries (e.g. In order to install capybara-webkit, we need to compile its source code on your computer. Depending on which Shell you’re using (the Mojave default is Bash), you’ll need to add the following line to your. Once we’ve installed Qt 5.5, we need to add its binaries to our system’s path, ensuring they can be found when we next try to build capybara-webkit. To ensure we have all the libraries we need, we must manually install an older version of Qt (version 5.5) via this link. Ordinarily we’d reach for MacOS’ unofficial package manager, Homebrew, to install our missing software, though the (newer) versions of Qt available via Homebrew no longer have the libraries that capybara-webkit requires. Our first step is to install the Qt libraries needed to compile and install capybara-webkit. The capybara-webkit gem depends on some software called Qt and won’t compile on MacOS without some QT libraries ( libqt) being present on your computer. Many Ruby on Rails projects use capybara-webkit to power their feature specs (tests that exercise their web app, including javascript, within a real browser environment). This post outlines the steps needed to install the capybara-webkit gem on a fresh copy of MacOS Mojave (10.14.6), hopefully saving you an hour of Google searching. As a Ruby on Rails developer, there’s a shortlist of Ruby gems that always seem to put a fight when I run bundle install and the capybara-webkit gem has proven to be one of the worst. I’ve recently upgraded to a Macbook Pro 2019 and need to setup my local development environment in MacOS Mojave.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |