Need IDE for embedded Linux project
A message that is not in the archive (sent off-list or not yet received): [email protected]
My pick: #4
Don't cross compile under Windows, you are setting yourself up for immense frustration and zero help. On the email lists and newsgroups, I've heard people ask several times whether it is possible to cross compile the linux kernel under CygWin and a few said they actually were going to do it -- but I have not heard any success stories.
As [email protected] said, use Samba -- your developers, who are familiar with Windows and Windows based editors, will be a lot less resistant to the move.
Check out VNC http://www.uk.research.att.com/vnc/ -- it is an open software "PCanywhere" type program that works very well under linux and quite well under Windows. Exceed (X windows on Microsoft Windows) is a nice program but pretty expensive.
The scheme is to have the files reside on the linux box. Each developer can use the tools of his choice to edit the files (Windows via Samba or native linux). Each developer would have a VNC connection or a simple telnet session (warning: Windows telnet really sucks) to do his builds using make.
gvb
Quoted 1 line · At 12:10 PM 1/21/2003 -0500, [email protected] wrote:
Hello all,
[snip]
Quoted 9 lines
As a first step I am trying to determine what IDE makes sense given our Department's infrastructure ... which is all windows (barf). I am aware of the following options:
Option 1: All Native Linux.
Option 2: Native windows cross development environment. Option 3: Vmware (linux guest on windows) with a Linux based IDE. Option 4: Linux development server <--> PC-X server software
(hummingbird) on windows development hosts.
[snip]
Quoted 12 lines
Thanks,
Brian Auld
Firmware EngineerBrian Auld
Embedded Software Engineer
ADIC
10 Brown Rd. Ithaca, NY 14850
(607) 241-4845
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Quoted 5 lines · Jerry Van Baren
The scheme is to have the files reside on the linux box. Each developer can use the tools of his choice to edit the files (Windows via Samba or native linux). Each developer would have a VNC connection or a simple telnet session (warning: Windows telnet really sucks) to do his builds using make.
Don't bother with MS telnet, use the Windows putty program as ssh client. Works great!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/