On Monday 16 November 2009, Alexander Neundorf wrote:
On Monday 16 November 2009, Emmanuel Blot wrote:
If the file needs to be preprocessed, set the LANGUAGE source file
property to C, this should work in most cases for now.
Yes they (many of them) do
Is there anyway in CMake to
Hi All,
I've just upgraded my CMake installation to 2.8.0, as my collegues
reported me some compilation errors with the new release of CMake
(they use Debian/unstable).
Before I'm able to reproduce the same error they got, I got another
error, on Mac OS X hosts.
It seems that CMake 2.8.0 forces
Emmanuel Blot wrote:
Hi All,
I've just upgraded my CMake installation to 2.8.0, as my collegues
reported me some compilation errors with the new release of CMake
(they use Debian/unstable).
Before I'm able to reproduce the same error they got, I got another
error, on Mac OS X hosts.
It seems
Can you create a bug entry for this?
Sure, I'll do it
As a quick fix I think if you set CMAKE_OSX_DEPLOYMENT_TARGET to empty it
will stop CMake form doing this. You should be able to do that either in
the cache or in your project.
Ok, it seems to work, thanks for the workaround.
Now the
On Monday 16 November 2009, Emmanuel Blot wrote:
Can you create a bug entry for this?
Sure, I'll do it
As a quick fix I think if you set CMAKE_OSX_DEPLOYMENT_TARGET to empty it
will stop CMake form doing this. You should be able to do that either in
the cache or in your project.
Ok,
On Monday 16 November 2009, Emmanuel Blot wrote:
If the file needs to be preprocessed, set the LANGUAGE source file
property to C, this should work in most cases for now.
Yes they (many of them) do
Is there anyway in CMake to tell something like all .S file should be
built with GCC or
