SlickEdit Product Discussion > SlickEdit®

SlickEdit OS Poll

(1/2) > >>

rwehrli:
What Operating System do you (mostly) use when running SlickEdit?

rwehrli:
This makes me curious as to what compiler/tool chains most Windows users are using behind SE.


Take Care.

Rob!

gavink:
To elaborate on my vote for Windows, we use the Greenhills C++ toolchain on Linux to compile for our 32-bit target code and also compile on Sun Solaris using the Sun Forte toolchain for our simulation and test code. Our projects for our smaller C projects with 8/16-bit micros usually use a Windows based compiler. To kick off our builds we either run the commands directly in Unix or we can do this automatically from SlickEdit using the rsh command. Unfortunately there is a bug with the Windows rsh implementation that makes that work not quite as well as it should, but it is good enough.

We use the Windows SlickEdit because most of us come from a Windows background and are comfortable there. Also it is cheaper. This causes some problems for some users when they save a file from SlickEdit/Windows through Samba to Unix and then hit compile but for some reason the date/time stamps are not quite right and the make file does not pick up on the file change. Again, this works good enough for most of the people most of the time.

hs2:
Use PuTTY tool suite instead of rsh etc. ! It's free and it's the best.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
HS2

j0hnw:

--- Quote from: rwehrli on July 12, 2006, 08:09:38 pm ---This makes me curious as to what compiler/tool chains most Windows users are using behind SE.

--- End quote ---

While it doesn't exactly answer your question to Windows users, we use OS X as our development "terminals". We then use the Intel compiler on a customized Debian build for most of our "backend" system code, and XCode (ie. gcc) for our frontend GUI tools.

      j0hnw

Navigation

[0] Message Index

[#] Next page

Go to full version