[CMake] CMake 2.6.2, Xcode and Fortran...

[Michael Jackson]

I can not comment on the Xcode stuff BUT have you tried to build your  
application using plain makefiles. I know it isn't as nice as an IDE  
BUT if it works with Makefiles then the problem is definitely one with  
Xcode project generation and not CMake in general.

Also, if you are not tied to Xcode AND makefiles will work for your  
needs then you can use Eclipse CDT instead of Xcode as an IDE. There  
is a CMake Wiki Entry for setting this up. Just presenting options.


_________________________________________________________
Mike Jackson                  mike.jackson at bluequartz.net
BlueQuartz Software                    www.bluequartz.net
Principal Software Engineer                  Dayton, Ohio

On Oct 14, 2008, at 8:38 AM, Dick Munroe wrote:

> Don't seem to play together well.
>
> I'm trying to use CMake because I've got a product that needs to be  
> build on Windows, Mac OS X and Linux.  I got the Windows port to  
> CMake done and am trying to get the Mac OS X version up in Xcode.   
> The configuration runs and creates the product but when any of  
> fortran code is compiled I get warnings:
>
>   warning: no rule to process file '/Users/dickmunroe/Documents/My  
> CVS/ESPlanner_Computation_Engine.U2008-11-01/Common/xmllib/print/ 
> test.for' of type sourcecode for architecture i386
>
> So I put manually put rules in for dealing with .for files which got  
> the compiles to work, but when I try to build projects now I get:
>
>   make: *** No rule to make target `/Users/dickmunroe/Documents/My  
> CVS/ESPlanner_Computation_Engine.U2008-11-01/ESPlanner Executables- 
> cmake/CMakeFiles/CMakeFORTRANCompiler.cmake', needed by `CMakeFiles/ 
> cmake.check_cache'.  Stop.
>
> And I clearly need to get a rule in place to hand this, but what  
> rule?  This is obviously generated by the CMake infrastructure so  
> why doesn't CMake either (1) add the rule directly to Xcode to get  
> this to work or (2) tell me what rule to add somewhere (which I'm  
> willing to do, but it sort of defeats the purpose of a build project  
> builder).  Of course, why doesn't CMake add the necessary rules for  
> fortran files in the first place...
>
> Best,
>
> Dick Munroe
>
> _______________________________________________
> CMake mailing list
> CMake at cmake.org
> http://www.cmake.org/mailman/listinfo/cmake