You will need wine-mono, wine-gecko, and optionally winetricks for your compiled version of wine. However, these packages may depend on the existing wine installation which may force you to remove them.
Warning: When you install a locally built version of Wine, the package management system will not know it exists since it did not come from a package. Thus it is possible to later break its dependencies or install a conflicting version of wine without a warning from the package management tools. You can prevent this by creating a package or by blocking conflicting packages with apt-pinning by setting "Pin-Priority: -1" for the packages.
Note: Many of the above commands require root privileges. Your user account needs to have access to root via sudo or you need to switch to a user account. Try configure with that line. It might be your trying to compile on 64 bit system a 32 bit wine and you will find that configure sometimes checks in wrong place for the libs.
Just install the default libfreetype6-dev , and libfreetype6:i , next make a link for the library. For unknown reason in one of my PCs I had a problem when the configure told an error in libfreetype6 , but it actually was libz and libpng.
Either way, you can solve the problem the same way. A general way to solve alike problems: open the config. You will find a code that have been used to test a presence of a library or headers. Just copy the main function with includes into a separate file; next seek above the code the command that was used to compile. It would look something like. That is basically the minimal test case, and once it is solved, the problem solved too.
Note: If you don't have pkg-config, please install it via sudo apt-get install pkg-config. If your problem is still not solved or it's related to something else , please debug your. And find the place of your problem e. If you have similar problem on Mac and you found this topic, please use homebrew to install your freetype package:.
If you still have the problem, check this bug. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Dialog text may be invisible or unaligned.
Use the --without-freetype option if you really want this. Re: configure: error: FreeType development files not found. Post by dimesio » Tue Apr 13, am vijay wrote: Hi I am a newbie,i am trying to install wine to my centos ,but am having these problems configure: error: FreeType development files not found. Post by vijay » Tue Apr 13, pm Ohhh So how to get the development files??? Thanks vijayanandkrishnan gmail.
Post by dimesio » Tue Apr 13, pm vijay wrote: Ohhh So how to get the development files?? Post by vitamin » Wed Apr 14, am vijay wrote: So how to get the development files? I built with stdenv on So don't get the b0rk. Same problem here on Mountain Lion.
I tried I see Installed with --universal on Wine upgraded to 1. I just hit this today. Warning: Clang currently miscompiles some parts of Wine.
Homebrew locked and limited conversation to collaborators Feb 16, Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in. If the application that you want working is not listed in the AppDB there is an easy to use form available for you to add it. If the application is in the database, but lacks a maintainer, you should consider volunteering. If you are familiar with Wine, own a legal copy of the application, and have a desire to test it, help get or keep it working, and help other users, please apply by clicking the link in the application's page.
Each application should have a supermaintainer, and, if different versions of the application are substantially different such as in Adobe Creative Suite , each subversion should have a maintainer. If you are the developer or publisher of the application, you obviously have a very big incentive to help get your application working under Wine. Fortunately, there are many options available to you other than reporting bugs and hoping someone will fix them.
By far the easiest way is to file a bug at Bugzilla , along with a small testcase to add to the Wine test suite. Another options is to send copies of your software to Wine developers and hope they'll take an interest in getting it working.
An alternative option, perhaps more effective, albeit expensive, is to pay Wine developers for their work on your application, either directly through a negotiated contract or indirectly by posting a bounty.
CodeWeavers, a major Wine developer, offers a special section for pledges at their compatibility center website. The most direct method, however, is to help develop Wine itself and contribute code directly, which is exactly what Corel did for! WordPerfect several years ago. In any case, making a post on the Wine developers email list can go a long way. If your application experiences problems in a particular area, or fails to even run at all, there are a number of steps you can take to help us.
0コメント