![]() ![]() NOW that was years ago and now after all this time they still can't even find the fortran compiler! talk about irresponsible they take the cake. ![]() it's a real problem as then it won't do anything - your like dead in the water for anything because u made the wrong references or associations even though u don't need them anyway for most things you do and then often a real pain having to go try and find the problem and 'undo' whatever u did wrong. And if u ever associate the wrong files etc libraries, command line options etc. but ofcourse no debugging capability for these. ![]() For example i do a simple compilation of a source file containing a module which is quite common in gfortran at the dos prompt and it compiles all in one step correctly with no problem but not with code::blocks even though i have it directed to use the same gfortran compiler though it can do simple fortran files with no modules and not requiring any other. and it complains can't find this and that and esp for fortran it's really difficult, impossible for me so far,to get all the references etc. Fairly good but it's really difficult- going round and round trying to set up 'tool chain executibles' etc.
0 Comments
Leave a Reply. |