AutoCad LT
From Wine-Wiki
AutoCad software is very popular and some view it as the standard to measure other Cad software.
There is a useful version history http://en.wikipedia.org/wiki/AutoCAD#Version_history
A lot of older versions are still in use, often because of dependency on older plug-ins.
There is apparently a recent [Jul 06] Linux Alternative that has been released
One Wine Developer opined: Missing AutoCAD Linux support has been a **MAJOR** [difficulty] for many years (piles and piles of requests), so it's very nice to finally see this resolved the right way (read: by direct competitors to AutoCAD [...]) There are several almost fully identically cloned CAD programs for Linux available (full AutoCAD interface with even slightly improved capabilities, so they're actually better), doing an internet search should help here ([...] BricsCAD was one of the major alternatives).
However Wine is continuing to progress despite companies who do not appear to show interest in supporting their users with Wine.
Contents |
[edit] Wine Application Database
As of May 2007 there are a number of entries in the application database.
- http://appdb.winehq.org/appview.php?appId=86
- http://appdb.winehq.org/appview.php?iVersionId=3321 Autocad LT 2004 currently rated poorly, but with an active maintainer
- http://appdb.winehq.org/appview.php?iVersionId=344 Autocad LT 1997 currently rated silver. without a maintainer. (please consider applying)
Bugzilla references for 2004 show some progress.
- Please consider submitting your test results for running this software under Wine.
| |
Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.
A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.
|
[edit] Links
[edit] External Links
- http://jnoter.blogspot.com/2007/05/come-installare-autocad-su-gnu-linux.html (Italian) appears to be a guide/howto..? reported on the wine-user mailing list
