Timeline for How to develop on Windows and test and run on Linux?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 2, 2011 at 22:59 | comment | added | Matthew Scharley | @c0ldcrow: Other than the file system issues, just be aware that depending on what you are doing, accessing files across a network to do dev work can be prohibitively slow. In particular, I've noticed that some version control systems are very slow when used on a network drive, though this particular case shouldn't be an issue for you (do all your source control stuff locally). | |
| Aug 2, 2011 at 20:05 | comment | added | c0ldcrow | Agree, this is the most useful and easiest option to implement. Configuring a VM the way I want it would require too much time. | |
| Aug 2, 2011 at 20:02 | vote | accept | c0ldcrow | ||
| Aug 2, 2011 at 13:23 | comment | added | bitsoflogic | Just beware of the differences in file systems. Windows doesn't support case-sensitive filenames (where "filename" and "FILENAME" are two different files), some chars as a filename (i.e. "/"), or soft links. | |
| Aug 2, 2011 at 13:17 | comment | added | Kristofer Hoch | This is the right answer. Especially if you can run Cygwin on your windows box; you can use Cygwin to display the Linux X-Windows (Gnome, KDE, Whatever the cool kids are using these days) back to your windows box. You can program in Eclipse directly on the Linux box and immediately test it. | |
| Aug 2, 2011 at 13:01 | history | answered | l0b0 | CC BY-SA 3.0 |