Hello,
I am sorry that it took me so long. I made an entry in mantis:
http://public.kitware.com/Bug/view.php?id=7919
2008/10/17 Alexander Neundorf <[EMAIL PROTECTED]>:
> Can you please post it again
> 1) as a patch
> 2) for the beginning without the modifications to the generators
>
> So we can ge
On Tuesday 14 October 2008, Andreas Pokorny wrote:
> Hello,
>
> 2008/10/14 Alexander Neundorf <[EMAIL PROTECTED]>:
> > [...]
> > For the files in Platform/ :
> >
> > Why did you create Generic-Windows.cmake and Generic-Windows-cl.cmake ?
> > Until now the "Generic-" prefix is used as the name of th
Hello,
2008/10/14 Alexander Neundorf <[EMAIL PROTECTED]>:
> [...]
> For the files in Platform/ :
>
> Why did you create Generic-Windows.cmake and Generic-Windows-cl.cmake ?
> Until now the "Generic-" prefix is used as the name of the "operating system"
> if there is no operating system (i.e. only
On Tuesday 14 October 2008, Alexander Neundorf wrote:
> On Friday 10 October 2008, Clemens Arth wrote:
> > Andreas,
> >
> > sorry but it took me a little longer to get the diff done, but now I
> > included some more things I found useful. Currently everything runs fine
> > for PPC2003,SP2003,WM5,WM
On Friday 10 October 2008, Clemens Arth wrote:
> Andreas,
>
> sorry but it took me a little longer to get the diff done, but now I
> included some more things I found useful. Currently everything runs fine
> for PPC2003,SP2003,WM5,WM6, and CE5.0, based on your configuration and
> some additional fl
Andreas,
sorry but it took me a little longer to get the diff done, but now I
included some more things I found useful. Currently everything runs fine
for PPC2003,SP2003,WM5,WM6, and CE5.0, based on your configuration and
some additional flags set - basically it's all in there what we (or at
leas
Andreas,
I'm sorry but I was wrong about the CE versioning for WM5 and WM6,
because the underlying CE versions are 5.01 and 5.02 (and not 5.1 and
5.2 I was assuming). Your original code works perfectly.
I have now used your WINCE templates and compiled for Smartphone
2003/PPC 2003 and WM5 Sm
Hello Clemens,
2008/9/30 Clemens Arth <[EMAIL PROTECTED]>:
> [...] I further modified your WinCE.cmake(-cl) configuration to
> WM5.cmake(-cl) to contain additional flags needed. Also a cached variable
> PLATFORM_SDKS is used that selects only those platforms from the set of all
> platforms install
Hi,
Is the code attached to this thread the most recent source code for
WinCE and Windows Mobile
support?
kind regards
Andreas
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Hi,
Andreas Pokorny schrieb:
Hello Clemens,
I still try to get some time slot to try your patches here. Since we
do not have that many 2005
licenses, I cannot do that as a kind of submarine project :).
2008/9/30 Clemens Arth <[EMAIL PROTECTED]>:
Andreas,
I had a look at your modified file
Hello Clemens,
I still try to get some time slot to try your patches here. Since we
do not have that many 2005
licenses, I cannot do that as a kind of submarine project :).
2008/9/30 Clemens Arth <[EMAIL PROTECTED]>:
> Andreas,
>
> I had a look at your modified files and, like the old ones, they
Andreas,
I had a look at your modified files and, like the old ones, they seem to
work quite well. However, there are some things that are somehow unclear
to me or cause problems here:
First, in WinCE.cmake, you replace the decimal string of the system
version CMAKE_SYSTEM_VERSION, which doe
Hi again
Or we let the user set n-different toolchain files each identifying an
individual
SDK (or maybe no toolchain files, just SDKs), and execute the CMakelists
multiple times using separate CMakeCaches.
that was definitely a good idea. Now I've predefined the names of
several different
Hi,
Andreas Pokorny schrieb:
Hello,
2008/9/19 Clemens Arth <[EMAIL PROTECTED]>:
[...]
I completely agree with you about the issue of adding and removing
individual files within a single solution, and I think the entire hack is
not a good solution. I would also prefer using an individual c
Hello,
2008/9/19 Clemens Arth <[EMAIL PROTECTED]>:
> [...]
>
>
> I completely agree with you about the issue of adding and removing
> individual files within a single solution, and I think the entire hack is
> not a good solution. I would also prefer using an individual cross compile
> configurati
Andreas,
well, considering the first issue I usually hoped that this might be
solved by Visual Studio somehow automatically by some internal magic.
After a cleanup of the WinCE.cmake and WinCE-cl.cmake a.s.o. these files
should mainly contain settings which are universal to all SDKs (I wonder
Hi,
I am still wondering how this all fits together.
The patch you are working on, will generate a visual studio file that
contains build rules for all installed SDKs.
But when generating for nmake we will have a cross compile
configuration for a single SDK. How can we ensure
that both things work
Am Thursday 18 September 2008 14:08:05 schrieb Andreas Pokorny:
> * If I am not mistaken there is yet no clean facility to specify the
> libpath and include path
> from the toolchain file
The lib path can normally be derived from the root path by specifying the
proper PATH_SUFFIXES when using f
18 matches
Mail list logo