The main reason why not run it is that if you build multiple builds of wxWidgets (eg, a dynamic debug one and a static release universal binary) it is easier for them to mix up each other when you install them to system-wide directories. So if you do make install the right call to wx-config will be /usr/local/bin/wx-config. But OS X searches /usr/bin before it does /usr/local/bin (you can check where wx-config runs from using whereis wx-config). Note: OS X 10.6 ships with wxWidgets and a wx-config already resides in /usr/bin, when you run make install the lib will be installed by default to /usr/local/lib and the wx-config to /usr/local/bin. Note that it may be necessary in dynamic builds if you do not set the -prefix as above, because dynamic libraries may not be found at runtime if they're in a local wx directory. Running make install is not necessary nor recommended in most cases. Make Install puts your wxWidgets build in a system-wide directory. Otherwise it is likely you will have mismatched files in your build directory. If you wish to rebuild the library (for example if you changed setup.h, or want to pass new flags to configure), it is recommended that you delete the entire build folder (eg, build-release) and start fresh with a new one. This is also where the corresponding wx-config is.įAQ What if I need to rebuild the library? The entire build takes about 6 minutes on a quad 2.66 GHz Power Mac.įollowing make, you will find the built library under your folder (eg, build-release).
0 kommentar(er)
