[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Managed make default config
|
Title: Message
Sean,
OK, I
see now.
Though one issue with that though is sharing projects between
users/workspaces will mean the projects always revert back to the default
configuration. We've tended to rely on that setting for providing
ready-made example projects for users to demonstrate some performance feature
such as DMIPS. The projects would be set to Release configs so the users could
just import them and run them out-of-the-box. Now this seems
like it would have to have a step to switch configs first
?
Any
comments as to whether this is a don't care or not for CDT/why the setting was
moved/if there's an easy workaround ?
Thanks,
Tracy
Tracy,
We store it as a persistent property on the
project now, so it is in the metadata for the workspace.
Sean Evoy
Rational Software - IBM Software
Group
Ottawa, Ontario, Canada
"Tracy Miranda"
<TMIRANDA@xxxxxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx
01/06/2005 08:47 AM
|
|
To
| <cdt-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
| [cdt-dev] Managed make
default config |
|
Hi,
With previous managed make (CDT 1.2) the .cdtbuild
file used to store info about which was the current configuration i.e Release
or Debug. Where is this information stored with the CDT 2.0 managed make ? -
it doesn't seem to be in the .cdtbuild file anymore
Thanks,
Tracy Miranda
