ha...@mac.com wrote:
Those id's are all over the place in projects. But, sounds like the
only ones that need to persist are the ones that represent files. I
suppose you could load in the existing project if there is one, and
populate a map of object id's for the files. You would have to write a
parser for the crazy Xcode file format. That would be the cleanest way
to do it, as the information is already on the disk. As Dave
mentioned, we don't have any funding for this right now, but you can
clone CMake, and give it a try. I can provide assistance if you want to
attempt this.
Thanks.
-Bill
isn't it easier to just query hash values from the file system( for
files that exist on disk) as the xcodeproj is generated? for nonexistent
files (build products) one has to find unique new ids - using the
current method. that would save us the xcodeproj parsing bit.
what expert time/funding are we talking?
That might work as well. You would have to come up with a hash that was
exactly this long: 218CE70218CE70218CE70000, and was always unique to
the file. But, if you did that it would work as well.
I am not sure what you are asking with the time/funding question?
-Bill
_______________________________________________
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_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
