[Adobe-source-devel] MSVC manifest file issues

[Foster T. B. <fbr...@ad...>]

ASL community,

Mat and I have been receiving several strange bugs where basic UI  
functionality isn't working at all. In each case when we try to  
regress them locally we are unable to reproduce the problem. Today  
Mat and I were researching a small warning we're getting from the  
resource compiler that the macro ADOBE_VER has been  declared twice.  
We have discovered that, when using bjam, the initialization code is  
executed twice and in each pass one or the other ADOBE_VER macro  
definition is globbed into the resource compiler settings. We suspect  
that bjam is making a pass over the configuration for each compiler  
it is trying to target (in our case, msvc 7.1 and msvc 8), but that  
the settings themselves are all getting globbed together. This would  
result in the possibility of the wrong manifest file being bound to  
an compiled binary, leaving it generally up in the air as to what  
compatibility issues may come out of it. It is this issue that we  
suspect may be at the heart of many of the UI problems we are seeing.  
I have sent an email off to the boost build mailing list in hopes of  
getting more information.

We are still in the process of exploring the bug and evaluating  
workarounds. If you are trying to build with BBv2 please consult  
their documentation regarding user-config.jam files. One possible  
(unverified) workaround is to remove usage of msvc-config from your  
user-config.jam and being explicit about which compiler you're  
targeting. We'll keep you posted as things come up.

Blessings,
Foster

--
Foster T. Brereton              <}}}><              Romans 3:21-26
A d o b e   S o f t w a r e   T e c h n o l o g y   L a b
"The fact is that the author of STL does not know how to write min,  
the author of C++ is not quite sure, and the standards committee is  
at a loss." -- Alexander Stepanov