Difference between revisions of "Talk:Compile EiffelStudio with Automatic Build Scripts"
| Line 5: | Line 5: | ||
: I have carified the documentation concerning the BASH issues. We have indeed experienced problems with the current version of BASH. AFAIK, it is a known issues, but I just could not google the source. I hope that is ok like that. Also I have added a reference to [[Installing Microsoft C compiler]]. --[[User:Schoelle|Schoelle]] 09:48, 15 March 2007 (CET) | : I have carified the documentation concerning the BASH issues. We have indeed experienced problems with the current version of BASH. AFAIK, it is a known issues, but I just could not google the source. I hope that is ok like that. Also I have added a reference to [[Installing Microsoft C compiler]]. --[[User:Schoelle|Schoelle]] 09:48, 15 March 2007 (CET) | ||
| + | |||
| + | --[[User:Jfiat|Jocelyn]] 16:26, 15 March 2007 (CET) | ||
| + | I think the bash issue had been fixed by setting the svn:eol-style to unix on the file "config.sh" (or related sh script files). I think this was the main issue with BASH compiling runtime ... So I guess there is no need to set any specific parameter to bash on windows anymore. | ||
Latest revision as of 06:26, 15 March 2007
--manus 05:43, 11 March 2007 (CET) Three things:
- On Windows, you should let follow the instructions at Installing Microsoft C compiler
- Is the bash version relevant?
- I always recommend installing cygwin using DOS/Windows style file otherwise you end up with text file that contains a mixture of DOS and Unix newline. So why do you need UNIX end of file?
- I have carified the documentation concerning the BASH issues. We have indeed experienced problems with the current version of BASH. AFAIK, it is a known issues, but I just could not google the source. I hope that is ok like that. Also I have added a reference to Installing Microsoft C compiler. --Schoelle 09:48, 15 March 2007 (CET)
--Jocelyn 16:26, 15 March 2007 (CET) I think the bash issue had been fixed by setting the svn:eol-style to unix on the file "config.sh" (or related sh script files). I think this was the main issue with BASH compiling runtime ... So I guess there is no need to set any specific parameter to bash on windows anymore.
