Bill Hoffman wrote:
Most files cmake writes out are copy if different. So, cmake writes a
file, then diff's it with the
file that was already there, and if they are different it gets rid of
the original and moves the new
file into place. This is to avoid too many reloads and other side
effects
Philip Lowman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Hoffman wrote:
Most files cmake writes out are copy if different. So, cmake writes a
file, then diff's it with the
file that was already there, and if they are different it gets rid of
the original and moves the new
fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Hoffman wrote:
> Philip Lowman wrote:
>> Does CMake do anything weird during it's configuration phase like write
>> out temporary files? Laying aside the initial compile checks which may
>> be occuring on the network drive (but if so, could be op
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Biddiscombe wrote:
> No real consolation or assistance, but I complained to our sysadmins
> that we had very slow builds from slave nodes, but fast from the master.
> I did some timing to give them something to aim for and it was
>
> Master node
No real consolation or assistance, but I complained to our sysadmins
that we had very slow builds from slave nodes, but fast from the master.
I did some timing to give them something to aim for and it was
Master node : configure+generate = 25 seconds (file system is fibre
channel or somethin
Philip Lowman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is it mostly sending time in try-compile stuff? If so, it might be
possible that we could add some sort of cmake temp directory that was
not under the build tree to run try-compile tests in. Then that could
be set t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill Hoffman wrote:
> Philip Lowman wrote:
>> We have somewhat of a large CMake project consisting of about 25
>> libraries. Configuring on Linux over NFS is a snap taking only a few
>> seconds. Configuring on a local C:\ for the Windows build is als
Philip Lowman wrote:
Hi,
We have somewhat of a large CMake project consisting of about 25
libraries. Configuring on Linux over NFS is a snap taking only a few
seconds. Configuring on a local C:\ for the Windows build is also
very fast only taking a few seconds.
When we go to configure a b
Hi,
We have somewhat of a large CMake project consisting of about 25
libraries. Configuring on Linux over NFS is a snap taking only a few
seconds. Configuring on a local C:\ for the Windows build is also very
fast only taking a few seconds.
When we go to configure a build on a remote file
