![]() Is it possible to have a dependency on a specific variant of another port? E.g.Portfile Development and Maintenance Questions.Why am I getting a message, "Warning… indications of -Wimplicit-function-declaration"?.Why am I getting an error about the wrong C++ runtime or libc++ or libstdc++?.Why can't I install both the " -devel" and non-" -devel" versions of a package?.How can I get a list of all dependencies for a port?.When should I use the force option (-f).Why do the python ports have so many dependencies?.Why is MacPorts using its own libraries?.Will MacPorts link to system libraries rather than its own?.What does 'Xlib: extension "RANDR" missing on display "/tmp/launch-XXXXXX/:0"' mean?.How should I report MacPorts issues encountered when using prerelease versions of macOS, Xcode, or Apple hardware?.Why has feature XYZ not been implemented yet, it is important?.What do I do if port selfupdate doesn't work or the rsync server refuses connections?.Where can I find a GUI frontend for MacPorts?.I get Error: checksum (md5/sha1/rmd160) mismatch for port.What are the folders in $/var/macports/ for and why do they take up so much space?.Can I install frameworks in /Library/Frameworks while using MacPorts?.Can I install software in /usr/local while using MacPorts?.Why is /opt/local the default install location for MacPorts?.Will my MacPorts install continue to work after installing a new major OS release or migrating to a new machine with a different CPU architecture?.I get the error "C compiler cannot create executables" or "ld: library not found for -lcrt1.10.6.o" or "can't read "build.cmd": Failed to locate 'make' in path" when I try to install a port.Does MacPorts always build from source?.The workaround for now is either to create and mount a case-insensitive disk image for craft usage or to manually create symlinks as needed.There is also a HOWTO section, which may answer some questions not listed here and provides useful tutorials for performing a number of different tasks using MacPorts. If you run into this issue, please reopen it! NOTE: The bug was closed due to a lack of information. When building craft packages on case-sensitive filesystem, you will see errors in packages referencing some of the KF5 libraries:įatal error: 'sonnet/highlighter.h' file not found In this shell, now craft is usable, e.g.Every time you want to use craft in a new shell, you need to set up the craft environment, first:.Note: At the time of this writing, with a fresh installation of Python 3.7 or 3.8, this command will fail with "certificate verify failed: unable to get local issuer certificate". Install Craft curl -o setup.py & python3 setup.py -prefix ~/CraftRoot Install XCode (at least developper command-line tools suffice):.Port variants kf5-kate # list available variants Many ports have additional variants, such as "+docs" for handbooks / API documentation: ![]() Sudo port install kf5-frameworkintegration # will get the most common frameworks in one go ![]() You can now start building frameworks or applications (if already packaged), using e.g. It is recommended that you build the patched Qt before any frameworks, in order to make extra sure all dependencies are resolved, correctly: Add the following line above any other path specifications (thus making sure it will take precedence): To do so, edit $/etc/macports/nf, where prefix is the root path of your MacPorts installation (/opt/local by default). # We assume you're doing this in your home directory Get the ports tree for patched qt and frameworks:.Note: If you have an existing installation of MacPorts and installed ports that depend on Qt, see this mail. ![]() Installation using patched version of Qt and MacPorts The main advantage is that most things can be expected to work out of the box. The main drawback with this is that Qt has to be compiled on your computer, adding hours to your setup time. There is some hope that the required patches will eventually become available in official Qt packages, but this is not the case as of this writing. It also follows the file system layout of KDE on Linux, which should mean that KDE applications will be more likely to work correctly, without adjustments. The latter has several patches meant to make KF5-applications work better on Mac. The two main approaches are using either a "stock" version of Qt, or a "patched" Qt. Several methods of building KDE / KF5 on Mac are available, and it is not firmly established, yet, which one is "best". 3.3 Case sensitive filesystem considerations.2 Installation using patched version of Qt and MacPorts. ![]()
0 Comments
Leave a Reply. |