Hello,
I have followed instructions in CMakeAddNewLanguage.txt [1] to add
support for Haskell, but I am a bit stuck on detecting dependencies
between source files. Haskell source compiles to a source file and an
"interface file" (similar to Fortran module file), which is needed for
compiling
Okay, thanks again for your help.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FA
On 03/15/2011 06:30 PM, arrowdodger wrote:
> On Tue, Mar 15, 2011 at 12:20 PM, Michael Wild wrote:
>
>> Just one warning: AFAIK these rule variables are only used for
>> Makefile-based generators, *NOT* for Xcode and VisualStudio and the
>> like. I'd prefer the route via add_custom_command/add_cu
On Tue, Mar 15, 2011 at 12:20 PM, Michael Wild wrote:
> Just one warning: AFAIK these rule variables are only used for
> Makefile-based generators, *NOT* for Xcode and VisualStudio and the
> like. I'd prefer the route via add_custom_command/add_custom_target...
>
> Michael
>
Oh, great, then i sh
On 03/15/2011 09:53 AM, arrowdodger wrote:
> On Tue, Mar 15, 2011 at 1:44 AM, Michael Hertling wrote:
>
>> To be exact, it's a rule variable which describes how to compile a C
>> source file to an object file. On my system, it currently expands to:
>>
>>-o -c
>>
>> AFAIK, these rule variable
On Tue, Mar 15, 2011 at 1:44 AM, Michael Hertling wrote:
> To be exact, it's a rule variable which describes how to compile a C
> source file to an object file. On my system, it currently expands to:
>
>-o -c
>
> AFAIK, these rule variables can be redefined and have the usual
> directory sco
On 03/14/2011 06:42 PM, arrowdodger wrote:
> On Mon, Mar 14, 2011 at 7:16 PM, Michael Hertling wrote:
>
>> 2) If you collect the affected files in a separate directory - which is
>> probably recommendable anyway - you might set CMAKE_C_COMPILE_OBJECT,
>> CMAKE_C_CREATE_SHARED_LIBRARY, CMAKE_C_
On Mon, Mar 14, 2011 at 7:16 PM, Michael Hertling wrote:
> 2) If you collect the affected files in a separate directory - which is
> probably recommendable anyway - you might set CMAKE_C_COMPILE_OBJECT,
> CMAKE_C_CREATE_SHARED_LIBRARY, CMAKE_C_LINK_EXECUTABLE etc. as well
> as their CXX coun
On 03/14/2011 03:15 PM, arrowdodger wrote:
> Hello. I'm using CMake as build system for a C/CXX project and i've faced
> the following problem: I need to compile some sources as bytecode for VM.
> This is achieved by using different linker (with different flags) and,
> probably, different compiler.
Hello. I'm using CMake as build system for a C/CXX project and i've faced
the following problem: I need to compile some sources as bytecode for VM.
This is achieved by using different linker (with different flags) and,
probably, different compiler. At the moment, the only solution i see is to
creat
10 matches
Mail list logo