On Friday 09 July 2010, Kishore wrote:
> On Wednesday 07 Jul 2010 8:54:52 pm Kishore wrote:
> > On Friday 02 Jul 2010 12:36:17 am Kishore wrote:
> > > On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> > > > On Thursday 01 July 2010, Kishore wrote:
> > > > > It seems that the PROJECT() c
On Wednesday 07 Jul 2010 8:54:52 pm Kishore wrote:
> On Friday 02 Jul 2010 12:36:17 am Kishore wrote:
> > On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> > > On Thursday 01 July 2010, Kishore wrote:
> > > > It seems that the PROJECT() command does a fair bit behind the scenes
> > > >
On Friday 02 Jul 2010 12:36:17 am Kishore wrote:
> On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> > On Thursday 01 July 2010, Kishore wrote:
> > > It seems that the PROJECT() command does a fair bit behind the scenes
> > > and is not documented enough. It seems to "reset" several var
On Friday 02 Jul 2010 12:07:07 am Alexander Neundorf wrote:
> On Thursday 01 July 2010, Kishore wrote:
> > It seems that the PROJECT() command does a fair bit behind the scenes and
> > is not documented enough. It seems to "reset" several variable created
> > before it was first called.
> >
> > Si
On Thursday 01 July 2010, Kishore wrote:
> It seems that the PROJECT() command does a fair bit behind the scenes and
> is not documented enough. It seems to "reset" several variable created
> before it was _first_ called.
>
> Since i use cmake from cross compilation, i have created Platform files f
It seems that the PROJECT() command does a fair bit behind the scenes and is
not documented enough. It seems to "reset" several variable created before it
was _first_ called.
Since i use cmake from cross compilation, i have created Platform files for
Generic-gcc.cmake and Generic-gcc-uc3b1256.c
