[CMake] [Dev] CMake 2.5-20070519 and tool chain support

Kishore, Jonnalagadda (IE10) Kishore.Jonnalagadda at honeywell.com
Thu May 24 10:14:18 EDT 2007


> -----Original Message-----
> From: cmake-bounces+kishore.jonnalagadda=honeywell.com at cmake.org
> [mailto:cmake-bounces+kishore.jonnalagadda=honeywell.com at cmake.org] On
> Behalf Of Alexander Neundorf
> Sent: Thursday, May 24, 2007 7:05 PM
> To: cmake at cmake.org
> Subject: Re: [CMake] [Dev] CMake 2.5-20070519 and tool chain support
> 
> On Wednesday 23 May 2007 12:38, kitts wrote:
> ...
> > And i just place them in the project folder? And pass the following
> > arguments to the cmake
> > command?"-DMCU=AT91RM9200
> > -DCMAKE_TOOLCHAIN_FILE=./Toolchain-Windows-IAR.cmake"
> >
> > AT91RM9200 because there are variants within the ARM architecture
and
> each
> > requires its own specific flags.
> 
> There is already the variable CMAKE_SYSTEM_PROCESSOR, which is
currently
> not
> used very much. I think this one could be reused for this purpose ?

Hmmm... Typically there are architectures and there are families for
each architecture. The "architecture" specifies the compiler for a given
toolchain and "family" for the specific flags. Every "processor" belongs
to a specific family and architecture.

So CMAKE_SYSTEM_PROCESSOR set to the exact part number could be used to
identify the architecture and family. But going this way IMHO is
difficult to maintain as one needs to keep track of the many processors
in the market. Maintaining architecture and family (variant) throws that
responsibility on the user and generally anyone working with them would
tend to have that amount of knowledge. Of course for ease with commonly
used processors, the CMAKE_SYSTEM_PROCESSOR could also be used!

Regards,
Kishore


More information about the CMake mailing list