[FIXED] An issue with TBB's 'version_string.tmp' file

[FIXED] An issue with TBB's 'version_string.tmp' file

I had an issue with TBB's 'version_string.tmp' file on a Windows platform.

The file was deleted by Windows Disk Cleanup utility because it has extension 'tmp' and the TBB build was broken:

...
..\\tbb40\\src\\tbb\\tbb_version.h(36) : fatal error C1083: Cannot open include file: 'version_string.tmp': No such file or directory
...

Since the file is used in the build process I would consider renaming it. Extensions like 'hxx', 'txx' or 'ver' could be considered instead.

PS: I recovered the file from a backup archive.

5 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.
Anton Malakhov (Intel)'s picture

Hi, SergeyHow do you build the library (which tools, versions, commands)? The .tmp file is really temporary because it is generated during the build process (by 'make'). And even if it is accidentally removed, it should be re-generated. The problem can lurk in broken dependencies rather than in the name.tmp.

Quoting Anton Malakhov (Intel)...
The problem can lurk in broken dependencies rather than in the name.tmp.
...

Hi Anton,

I just tried to re-build 'tbb', 'tbbmalloc' and 'tbbmalloc_proxy' projects in VS 2005( Debug &Release
configurations )with a 'version_string.tmp' removed. I've expected that it would be re-created. No, it wasn't.

Here are some technical details:

TBB version 4.0
Visual Studio 2005

Outputs are as follows:

------ Build started: Project: tbb, Configuration: Debug Win32 ------
Compiling...
tbb_misc.cpp
c:\aaa\tbb40\src\tbb\tbb_version.h(36) : fatal error C1083: Cannot open include file: 'version_string.tmp': No such file or directory
tbb - 1 error(s), 0 warning(s)
------ Build started: Project: tbbmalloc, Configuration: Debug Win32 ------
Compiling...
tbbmalloc.cpp
c:\aaa\tbb40\src\tbbmalloc\../tbb/tbb_version.h(36) : fatal error C1083: Cannot open include file: 'version_string.tmp': No such file or directory
tbbmalloc - 1 error(s), 0 warning(s)
------ Build started: Project: tbbmalloc_proxy, Configuration: Debug Win32 ------
Compiling resources...
../../src/tbb/tbb_version.h(36) : fatal error RC1015: cannot open include file 'version_string.tmp'.
tbbmalloc_proxy - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 3 failed, 0 up-to-date, 0 skipped ==========

------ Build started: Project: tbb, Configuration: Release Win32 ------
Compiling...
tbb_misc.cpp
c:\aaa\tbb40\src\tbb\tbb_version.h(36) : fatal error C1083: Cannot open include file: 'version_string.tmp': No such file or directory
tbb - 1 error(s), 0 warning(s)
------ Build started: Project: tbbmalloc, Configuration: Release Win32 ------
Compiling...
tbbmalloc.cpp
c:\aaa\tbb40\src\tbbmalloc\../tbb/tbb_version.h(36) : fatal error C1083: Cannot open include file: 'version_string.tmp': No such file or directory
tbbmalloc - 1 error(s), 0 warning(s)
------ Build started: Project: tbbmalloc_proxy, Configuration: Release Win32 ------
Compiling resources...
../../src/tbb/tbb_version.h(36) : fatal error RC1015: cannot open include file 'version_string.tmp'.
tbbmalloc_proxy - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 3 failed, 0 up-to-date, 0 skipped ==========

So, there is a compilation error C1083 and a resource compiler error RC1015.

Thecompilation order is ( in Debug & Release ):

'tbb'
'tbbmalloc'
'tbbmalloc_proxy'

Best regards,
Sergey

Quoting Anton Malakhov (Intel)...
The .tmp file is really temporary because it is generated during the build process (by 'make')
...

Here are a couple of more tips:

- I remember that the file existed from the very beginning. As soon as I've installed TBB v4.0 on my computer I've noticed the 'version_string.tmp' file;

-In case ofTBB I always use IDE-based build and never used a command-line build with 'make'.

>>...I had an issue with TBB's 'version_string.tmp' file on a Windows platform...

Simply to report that in TBB v4.1 Update 1 the problem is fixed and version_string.tmp file is renamed to version_string.ver.

Thank you.

Login to leave a comment.