> Usually there are 2 ways: 1) put them into separate directories (like Debug
> and Release), probably specifying different output directories or 2) use
> different file names, say adding suffixes like D, or d8.
> BTW, what's the point to have different configurations in the same workspace
> (do y
Hi Alexey,
Usually there are 2 ways: 1) put them into separate directories (like Debug
and Release), probably specifying different output directories or 2) use
different file names, say adding suffixes like D, or d8.
BTW, what's the point to have different configurations in the same workspace
(d
2011/3/4 Alexey Livshits :
>> I am not a Visual Studio user so I may be missing your point here
>> but why having foo_1 and foo_2 ending up in the same workspace is a problem?
>>
>> As long as the lib/dll end up in separate dirs (using *_OUTPUT_DIRECTORY).
>
> Workspaces become too large, so I woul
> I am not a Visual Studio user so I may be missing your point here
> but why having foo_1 and foo_2 ending up in the same workspace is a problem?
>
> As long as the lib/dll end up in separate dirs (using *_OUTPUT_DIRECTORY).
Workspaces become too large, so I would like make'em smaller.
> Should
2011/3/4 Alexey Livshits :
>> You can definition two different library target
>> and use OUTPUT_NAME property to adjust the name
>>
>> add_library(foo1 ${foo_source})
>> set_target_properties(foo1 PROPERTIES
>> OUTPUT_NAME foo)
>>
>> add_library(foo2 ${foo_sour
> You can definition two different library target
> and use OUTPUT_NAME property to adjust the name
>
> add_library(foo1 ${foo_source})
> set_target_properties(foo1 PROPERTIES
> OUTPUT_NAME foo)
>
> add_library(foo2 ${foo_source})
> set_target_properties(foo2 P
2011/3/3 Alexey Livshits :
> Hello CMakers,
> suppose I've got a library foo with tow configurations: foo_1 and
> foo_2. Both versions should have the same output name: foo. The
> problem is, the output directory for both ist the same, so the second
> will overwrite the first.
You can definition t
Hello CMakers,
suppose I've got a library foo with tow configurations: foo_1 and
foo_2. Both versions should have the same output name: foo. The
problem is, the output directory for both ist the same, so the second
will overwrite the first.
What's the best way to organize it?
--
BG,
Alexey
__
