CMake:OpenTasks: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 46: Line 46:
* fine grained flags (per source etc.), AFAIK is being worked on
* fine grained flags (per source etc.), AFAIK is being worked on


* something like BREAK and/or RETURN to break from loops, makros, functions and  
* something like BREAK and/or RETURN to break from loops, makros, functions and files. This should make some code easier to read and write ([http://www.cmake.org/Bug/view.php?id=3612  #3612]).
files. This should make some code easier to read and write ([http://www.cmake.org/Bug/view.php?id=3612  #3612]).


* better (PCDR) regexps, is being worked on
* better (PCDR) regexps, is being worked on


* abstraction of compiler flags (being worked on ?)
* abstraction of compiler flags (being worked on ?)

Revision as of 22:16, 20 December 2007

Support for major buildsystems

Supported:

  • make, MSVC, XCode, Eclipse, KDevelop, CodeBlocks

Missing:

  • Some generic file format, maybe XML based, so that it would be easy to process. Maybe ant may be a good candidate. This might also help the Java support in CMake. Any takers ?

Support for programming languages

Fully supported:

  • C, C++

More or less fully supported:

  • Fortran: some dependency issues, is currently being worked on
  • C#: what's the current status ?
  • Java: there may be some issues relating to Java packages and subdirectories
  • Assembler: is in CMake cvs, but needs more testing and feedback
  • Ada: not yet in cvs, but support exists (in PlPlot)
  • Objective C: may work if the compiler (gcc) knows how to handle these files

Not supported:

  • Pascal: shouldn't be too hard, volunteers ?
  • OCaml: really strange to build, may be hard to integrate

Operating systems

Supported:

  • all major OSs, except the ones listed below

Need improvement:

  • OpenBSD: library versioning scheme #2470

Not supported:

  • VMS, OS/2, DOS, DJGPP

CMake language features

  • parentheses in conditions: if((a OR b) AND (c OR d))

I guess square brackets would be acceptable too (just in case this would easier for the parser): if( [a OR b] AND [c OR d] ) (#6191)

  • some way to define custom command line arguments
  • fine grained flags (per source etc.), AFAIK is being worked on
  • something like BREAK and/or RETURN to break from loops, makros, functions and files. This should make some code easier to read and write (#3612).
  • better (PCDR) regexps, is being worked on
  • abstraction of compiler flags (being worked on ?)