gEDA for Windows?
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||||||||||||||
|
Posted by Joerg on October 30, 2007, 4:17 pm
Please log in for more thread options compile a Windows version containing some of the gEDA modules. But somehow that seems to always fizzle. Is there a realistic chance we'll ever see a somewhat "official" Windows version? Maybe along the lines of "Here, use it but please don't call us for support." I know that it's possible to compile it for Windows. However, lots of us are more hardware guys, don't have compilers, don't have much experience doing that, and would need something that installs itself just like other CAD software does. After that we could be productive for the group by contributing library models, tricks and so on. For many reasons hardware guys can't migrate away from Windows, mainly because things like the mechanical CAD, beamfield simulators and the like would then quit. -- Regards, Joerg http://www.analogconsultants.com/ | ||||||||||||||||||||||||||||
|
Posted by Cesar Strauss on October 30, 2007, 6:25 pm
Please log in for more thread options It's one of my goals to compile the Windows version of some of the gEDA tools, starting with the schematics editor and the pcb layout tool. I'm not part of the core team of developers, but I do contribute some source code to the project, with that goal. > Is there a realistic chance we'll ever see a somewhat "official" Windows
> version? Maybe along the lines of "Here, use it but please don't call us > for support." I think there is a good chance. Not only that, I'll be glad to answer Windows-related questions posted here or at the gEDA user mailing list. I expect others would help as well. > I know that it's possible to compile it for Windows.
Almost possible, I'll say. Much work has already been done, but a few minor user-visible issues remain. I would not wish to make available a Windows version until most of these are solved, it could impact negatively on the reputation of the project as a whole. But it's only a matter of Time. > However, lots of us
> are more hardware guys, don't have compilers, don't have much experience > doing that, and would need something that installs itself just like > other CAD software does. Very understandable. > After that we could be productive for the group
> by contributing library models, tricks and so on. That would be great. > For many reasons
> hardware guys can't migrate away from Windows, mainly because things > like the mechanical CAD, beamfield simulators and the like would then quit. I know that feeling... Regards, Cesar | ||||||||||||||||||||||||||||
|
Posted by Joerg on October 30, 2007, 8:04 pm
Please log in for more thread options Cesar Strauss wrote:
> Joerg wrote:
>> Since quite a while I see a hint here or there that someone wants to
>> compile a Windows version containing some of the gEDA modules. But >> somehow that seems to always fizzle. >
> It's one of my goals to compile the Windows version of some of the > gEDA tools, starting with the schematics editor and the pcb layout > tool. I'm not part of the core team of developers, but I do contribute > some source code to the project, with that goal. > >> Is there a realistic chance we'll ever see a somewhat "official" Windows
>> version? Maybe along the lines of "Here, use it but please don't call us >> for support." >
> I think there is a good chance. Not only that, I'll be glad to answer > Windows-related questions posted here or at the gEDA user mailing > list. I expect others would help as well. > >> I know that it's possible to compile it for Windows.
>
> Almost possible, I'll say. Much work has already been done, but a few > minor user-visible issues remain. I would not wish to make available a > Windows version until most of these are solved, it could impact > negatively on the reputation of the project as a whole. But it's only > a matter of Time. > So there is hope. That is great to hear. It may be ok to release something that's not perfect if it clearly says so on the download page. Maybe with some hints as to what might not quite work yet. >> However, lots of us
>> are more hardware guys, don't have compilers, don't have much experience >> doing that, and would need something that installs itself just like >> other CAD software does. >
> Very understandable. > >> After that we could be productive for the group
>> by contributing library models, tricks and so on. >
> That would be great. > >> For many reasons
>> hardware guys can't migrate away from Windows, mainly because things >> like the mechanical CAD, beamfield simulators and the like would then quit. >
> I know that feeling... > Almost every week someone tells me to use Linux and all the crashes and stuff would go away. Then I ask them whether my .NET driven scope would still work. "Umm, probably not." Incompatibility actually goes as far as Vista. Several of the SW packages I use are almost guaranteed not to work there. At least that's what the mfgs said. Luckily one can still buy XP (done that again about a month ago). -- Regards, Joerg http://www.analogconsultants.com/ | ||||||||||||||||||||||||||||
|
Posted by Joel Koltner on October 31, 2007, 12:49 pm
Please log in for more thread options > Almost every week someone tells me to use Linux and all the crashes and
> stuff would go away. That's optimistic anyway -- buggy software has a lot more to do with the guy who programmed it than the particular operating system it's running on. Windows "blue screens" (OS crashes) are about as rare as Linux kernel panics (crashes) these days. (Although when it comes to Vista they made so many changes that you can't really accept Microsoft's claim that it's a "compatible" operating system with XP... :-( ) Have you looked at virtualization software such as VMware? Let's you run Windows and Linux (and other OSes) all side by side on the same box. | ||||||||||||||||||||||||||||
|
Posted by Joerg on October 31, 2007, 1:04 pm
Please log in for more thread options Joel Koltner wrote:
>> Almost every week someone tells me to use Linux and all the crashes and
>> stuff would go away. >
> That's optimistic anyway -- buggy software has a lot more to do with the guy > who programmed it than the particular operating system it's running on. > Windows "blue screens" (OS crashes) are about as rare as Linux kernel panics > (crashes) these days. (Although when it comes to Vista they made so many > changes that you can't really accept Microsoft's claim that it's a > "compatible" operating system with XP... :-( ) > According to compatibility notices from several mfgs of software I use it definitely isn't 100% compatible. Which is why I don't use Vista. > Have you looked at virtualization software such as VMware? Let's you run
> Windows and Linux (and other OSes) all side by side on the same box. > I've only heard that it can take a long time to make everything work in the box, virual RS232 over USB and such vital things. But no, I haven't tried yet. Basically Windows does everything I need. -- Regards, Joerg http://www.analogconsultants.com/ | ||||||||||||||||||||||||||||
| Similar Threads | Posted |
| gEDA for Windows? | October 30, 2007, 4:17 pm |
| Klik & gEDA | May 16, 2006, 10:07 pm |
| New gEDA release (20041228) available | December 31, 2004, 7:06 pm |
| gEDA project in EE Times today! | December 14, 2004, 4:57 am |
| gEDA project in EE Times today! | December 15, 2004, 10:51 am |
| geda/gschem setup problems | April 18, 2005, 8:53 pm |
| gschem/pcb (geda) simm72 correct? | May 25, 2006, 11:48 am |
| gEDA suite vs my creaky old Protel Client 3.5? | April 27, 2005, 10:51 am |
| gEDA gschem: "Write image" resolution | October 7, 2008, 9:13 pm |
| gEDA Binary Suite released and Google Summer of Code 2008 | March 28, 2008, 11:26 pm |
| LTspice is only for windows | August 8, 2004, 6:00 pm |
| orcad9.0 under windows XP | February 24, 2006, 4:42 am |
| Generic CADD for Windows | February 9, 2005, 4:23 am |
| Windraft running on Windows XP | June 12, 2005, 10:23 am |
| OT: Copy PATH from Windows Explorer ?? | December 20, 2004, 1:17 pm |
> compile a Windows version containing some of the gEDA modules. But
> somehow that seems to always fizzle.