Re: [Adobe-source-devel] No build scrips for version 1.0.20 work on Win32

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

Hi Elisha,

On Sep 25, 2006, at 2:18 PM, Elisha Berns wrote:

> I have tested repeatedly the automated build scripts for ASL on =20
> Win32 using
> both VC71 and VC80 and neither works.  The script downloads, unzips =20=

> and
> patches and then cannot build several targets.  Using the VC80 =20
> solution
> file(s) does not work either (see attached file).
>
> Can someone either fix these issues in the sources or help me =20
> resolve the
> issues?

I'd be happy to help you to resolve the issue you are seeing. One of =20
the most prevalent issues you have is:

> warning C4819: The file contains a character that cannot be =20
> represented in the current code page (1255). Save the file in =20
> Unicode format to prevent data loss

We have seen this once before: the issue started with the sources =20
being compiled on a WinXP machine whose region was set to something =20
other than the United States. The problem arose when the compiler ran =20=

across a character it could not translate to the code pages for the =20
region set on the build machine. Most of the issues we found revolved =20=

around high-ASCII characters in the names of the authors of the =20
sources. The most annoying part was that these characters are often =20
found only in comments, which need not be considered by the compiler =20
in the first place! We have notified Boost of this issue in the past, =20=

but I get the impression a fix is very low on their priority list. =20
Nevertheless, there is a simple workaround: delete the offending =20
character from the source file. If you can give me line numbers in =20
the files where this is an issue, I can modify our Boost patch file =20
to eliminate the violating characters for the next release.

If this is not the issue you are seeing, please provide a little more =20=

detail about the build environment under which you are compiling the =20
sources. If you can hack the automated build script and change =20
instances of 'bjam' to 'bjam -d2', you should get copious debugging =20
information during a build -- such information would also help.

I'm available to continue working with you on resolving this issue. =20
Please keep me informed. Thanks again for your interest in ASL!

Blessings,
Foster


--
Foster T. Brereton              <=E1=BC=B0=CF=87=CE=B8=CF=8D=CF=82><     =
         Romans =20
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
"What 99 percent of programmers need to know is not how to build =20
components but how to use them." -- Alexander Stepanov