[CMake] Object files: .o vs .obj?

[Phil Smith]

Hm. If I do an out-of-source build, I get .o files.  If I do an in-source build, I get .obj.

(Yes, I know in-source builds are considered Evil; the lead engineer wants to do 'em that way, not sure why, so I was testing to see if they'd work, noticed that I was getting .obj files.)

Does this make any sense?

...phsiii
-----Original Message-----
From: cmake-bounces at cmake.org [mailto:cmake-bounces at cmake.org] On Behalf Of Phil Smith
Sent: Thursday, October 09, 2008 12:27 PM
To: CMake
Subject: [CMake] Object files: .o vs .obj?

With (allegedly) identical CMake setups, we have two machines that generate different outputs: .o vs. obj. The one that generates .obj has Visual Studio installed, the other doesn't.

I tried adding
        SET(CMAKE_C_OUTPUT_EXTENSION ".obj")
to my Toolchain file, but it made no difference.

The CMake invocation is:

cmake -DCMAKE_TOOLCHAIN_FILE:string="%DIGNUS_SOURCE%\zosport.cmake" -G"Unix Makefiles" %DIGNUS_SOURCE%\vtk-core\

I even added:
 message(STATUS "Generator is ${CMAKE_GENERATOR}")
in the ".obj" machine's CMakeLists.txt (that's the machine with Visual Studio installed), again, no difference.

I'd slightly rather force .obj than .o, but in any case, I need it to be predictable. Any ideas?
--
...phsiii

Phil Smith III
phil at voltage.com
Voltage Security, Inc.
www.voltage.com
(703) 476-4511 (home office)
(703) 568-6662 (cell)

_______________________________________________
CMake mailing list
CMake at cmake.org
http://www.cmake.org/mailman/listinfo/cmake