At 04:07 AM 5/29/2006, Sylvain Benner wrote:
>
>Hi Phillip,
>
>Moreover the compilation time is bigger when it prints all this "compiling..."
>lines.
>In our custom generator we don't specify any Object File and it works great.
>Here is the replacement we made in our cmLocalVisualStudio7Generator :
>
>//if(objectName.size())
>// {
>// fout << "\t\t\t\t\tObjectFile=\"$(IntDir)/"
>// << objectName.c_str() << "\"\n";
>// }
>fout << "\t\t\t\t\tObjectFile=\"$(IntDir)/\"\n";
>
>I don't know about conflicting names but I guess that VS.net has his own way
>to name the object files and so can perform some optimization during
>compilation time.
>I did the test several times and without object file names specified we save
>up to 20 seconds per full compilation process on only one project. It's huge.
>It would be good that someone else tests this to be sure I'm not going mad.
>
>Anyway I guess that for VS.net projects it's not necessary to name the object
>files, when you open a .vcproj generated by a wizard, it never specify any
>object file name (most of the time there is even no FileConfiguration
>element). Conflicting filenames should never occur if you let VS.net handles
>the naming.
>
OK, if you add conflicting file names via the wizard, it will set the object
name.
That is how I found out how to fix the problem...
However, it seems to have a performance impact if you do it all the time.
I will look at changing it so it will only do this only
when there is a conflicting name.
-Bill
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
