On 2010-08-12 17:36-0700 J Decker wrote:
To Reiterate steps
--
mkdir /test
touch /test/CMakeLists.txt
mkdir /build
cd /build
[cmake-gui /test] or [cmake -G "MinGW Makefiles" /test]
touch /test/CMakeLists.txt
make
(fails)
In the past I found a subdirectory of the source tree name
On 8/12/10 1:51 PM, Chris Wolf wrote:
On 8/12/10 1:30 PM, Óscar Fuentes wrote:
Michael Wild writes:
How to know the compiler arguments set by include_directories,
add_definitions, etc?
CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
doesn't contain anything that was set by
2.8.1 also does this
I thought it was because i didn't specify the drive, because I'm
pretty sure I did this a lot when first developing cmakelists for my
projects... but I don't know maybe 2.8.0 did it differently and I
don't have that anymore... maybe I had the cmake-gui up and kept
hitting gene
Hi,
On 2010/08/12, at 20:15, Chris Wolf wrote:
>
>
> On 8/12/10 10:20 AM, Carlos Gonçalves wrote:
>> Hi,
>>
>> I have already looked everywhere possible (so to speak) on how to create a
>> Framework + Unix tools as described in [1] but found no examples. So far I
>> was able to create a Fram
I have a project which creates a shared library and a utility which uses this
shared library. I would like to be able to run the utility within the build
tree and also from the final install directory. I can do this, it works,
but the path hard-coded path in the executable is always the build tre
On 8/12/10 10:20 AM, Carlos Gonçalves wrote:
> Hi,
>
> I have already looked everywhere possible (so to speak) on how to create a
> Framework + Unix tools as described in [1] but found no examples. So far I
> was able to create a Framework only [2].
>
> I'm trying to add Mac OS X support to G
On 8/12/10 1:30 PM, Óscar Fuentes wrote:
> Michael Wild writes:
>
How to know the compiler arguments set by include_directories,
add_definitions, etc?
CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
doesn't contain anything that was set by the cmake comm
Michael Wild writes:
>>> How to know the compiler arguments set by include_directories,
>>> add_definitions, etc?
>>>
>>> CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
>>> doesn't contain anything that was set by the cmake commands mentioned
>>> above.
>>
>> I guess that the l
On 12. Aug, 2010, at 15:59 , Óscar Fuentes wrote:
> Óscar Fuentes writes:
>
>> How to know the compiler arguments set by include_directories,
>> add_definitions, etc?
>>
>> CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
>> doesn't contain anything that was set by the cmake com
Hi,
I have already looked everywhere possible (so to speak) on how to create a
Framework + Unix tools as described in [1] but found no examples. So far I was
able to create a Framework only [2].
I'm trying to add Mac OS X support to GeneratorRunner[3] and my current
CMakeLists.txt can be viewe
Óscar Fuentes writes:
> How to know the compiler arguments set by include_directories,
> add_definitions, etc?
>
> CMAKE__FLAGS (with and whitout the uppercase build_type suffix)
> doesn't contain anything that was set by the cmake commands mentioned
> above.
I guess that the lack of response in
11 matches
Mail list logo
