Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] ids in .cproject

Johannes,

You should also consider manipulating your projects at the object-model level, instead of the .cproject text-file level.  As I understand it, the format of the .cproject file is an implementation detail that is likely to change in the future.  For our product, we've implemented a similar project-migration feature at the object-model level using only public APIs.

- Baltasar


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Kogler Johannes
Sent: Friday, August 14, 2009 8:04 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] ids in .cproject

Hi Andrew,

thanks for your response! If I understand correctly, that means that it would be possible to generate such an unique id.

Best regards,
Johannes


From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Gvozdev
Sent: Friday, August 14, 2009 1:04 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] ids in .cproject

Hi Johannes,
The project model keeps track of numerous objects generated by it using objects ids. To tell apart those - unique numeric values are appended. In case where there are 2 numbers like "cdt.managedbuild.tool.gnu.c.compiler.exe.debug.2129512843.912733452" - the first number is id of parent and the second is own id. (i.e. id of parent is taken and unique number is appended while constructing the object).

Hope that helps,
Andrew
On Fri, Aug 14, 2009 at 1:59 AM, Kogler Johannes <Johannes.Kogler@xxxxxxxxxxxxx> wrote:
Hi,

we prepare the migration of our managed build projects from our current
IDE to Eclipse CDT. Therefore we read all project build properties for
all configurations from the project description files of our IDE and try
to extend the .cproject files with the equivalent settings.

Here is an extract of the .cproject file for build properties set on the
file ABCTest.c:

...
<fileInfo
id="cdt.managedbuild.config.gnu.exe.debug.1338609081.761170479" name="
ABCTest.c" rcbsApplicability="disable" resourcePath="src/ABCTest.c"
toolsToInvok
e="cdt.managedbuild.tool.gnu.c.compiler.exe.debug.2129512843.912733452">
<tool
id="cdt.managedbuild.tool.gnu.c.compiler.exe.debug.2129512843.912733452"
n
ame="GCC C Compiler"
superClass="cdt.managedbuild.tool.gnu.c.compiler.exe.debug.
2129512843">
<option id="gnu.c.compiler.option.preprocessor.def.symbols.353474233"
superClass
="gnu.c.compiler.option.preprocessor.def.symbols"
valueType="definedSymbols">
<listOptionValue builtIn="false" value="DEBUG_DEFINE"/>
<listOptionValue builtIn="false" value="DEBUG_DEFINE2"/>
</option>
<inputType id="cdt.managedbuild.tool.gnu.c.compiler.input.2143323675"
superClass="cdt.managedbuild.tool.gnu.c.compiler.input"/>
</tool>
...

The readable id "cdt.managedbuild.config.gnu.exe.debug" is extended by
the numeric values "1338609081.761170479". Could anybody explain me how
these values are generated?

Thanks in advance!
Johannes
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev



Back to the top