| Author |
Message |
Index > Technical Support ~ More help getting a Rails environment setup under Cygwin |
| charlesroper |
 Posted: Sun Mar 18, 2007 12:09 pm |
 |
|
Registered User
Joined: 06 Mar 2007
Posts: 1204
Location: UK
|
Thought I'd share this link, which looks like it could come in handy for those looking to get a Rails environment setup under Cygwin:
http://garbageburrito.com/blog/entry/240
One issue that I fell foul of that isn't mentioned anywhere else (that I could find): as you're installing gems under Cygwin, be sure to install the Ruby versions. As I discovered, the mswin32 versions simply don't work under Cygwin. The Ruby versions come with their own gotchas too though: they try to compile stuff, so you'll need to make sure you have the make and gcc-core installed at least if you want to install mongrel. |
|
|
| Back to top |
  
|
| thabenksta |
| Posted: Fri Mar 23, 2007 6:52 pm |
|
|
|
Registered User
Joined: 23 Mar 2007
Posts: 9
|
That's me! I also just happen to have switched to e as my editor. e and cygwin really make a good Rails dev environment.
The only thing I had to do special for e was make a little shell script that opens e in the background, so I can say and open the current dir as a project.
Very sweet. |
|
|
| Back to top |
|
| charlesroper |
| Posted: Fri Mar 23, 2007 8:01 pm |
|
|
|
Registered User
Joined: 06 Mar 2007
Posts: 1204
Location: UK
|
Hey Ben, welcome.
I've done a similar thing: I added e to my Windows PATH (which gets imported into Cygwin automatically). Unfortunately, running e from Cygwin locks it out until e has closed again. The solution? I just added alias e='cygstart e' to my .bashrc and voilą, job done. 
One thing that doesn't work with e, but does with TM is piping. E.g.
The result of the ls should end up in e, but it doesn't. |
|
|
| Back to top |
|
| thabenksta |
| Posted: Fri Mar 23, 2007 8:36 pm |
|
|
|
Registered User
Joined: 23 Mar 2007
Posts: 9
|
| Nice, I was unaware of cygstart. That will definitely come in handy. |
|
|
| Back to top |
|
| makingme |
| Posted: Sat Mar 31, 2007 6:05 pm |
|
|
Registered User
Joined: 03 Jan 2007
Posts: 270
Location: Minneapolis, MN
|
I've added E to my windows path and its not working, any help or more indepth instruction would be cordially welcomed!
Thanks. |
|
|
| Back to top |
|
| charlesroper |
| Posted: Sat Mar 31, 2007 6:06 pm |
|
|
|
Registered User
Joined: 06 Mar 2007
Posts: 1204
Location: UK
|
|
| Back to top |
|
| makingme |
| Posted: Sat Mar 31, 2007 6:30 pm |
|
|
|
Registered User
Joined: 03 Jan 2007
Posts: 270
Location: Minneapolis, MN
|
Thanks, works like a charm. I made a mistake when adding the path, I added the actual c:\..\e\ e.exe as well as opposed to just saying c:\..\e\ .
UGH! I hate when I make dumb mistakes like that. |
|
|
| Back to top |
|
| Fafner |
| Posted: Sat May 05, 2007 7:15 pm |
|
|
|
Registered User
Joined: 05 May 2007
Posts: 13
|
charlesroper wrote: Did you reboot?
Alternatively, you can download SP2 Support Tools from Microsoft and use a utility called setx.
Code: setx path "%PATH%;c:\Program Files\e"
No reboot needed, you only need to open a new console window for the path variable to be loaded. |
|
|
| Back to top |
|
| pnomolos |
| Posted: Mon May 07, 2007 3:50 pm |
|
|
|
Registered User
Joined: 22 Feb 2007
Posts: 136
|
| You don't normally have to reboot for environment variables to "stick" - you just need to start a new console window (unless that's a 'feature' of XP Pro over Home?) |
_________________
"I'm so retro I was cool before being cool was cool." |
|
| Back to top |
|
|
|
