Skip Menu |
 

Subject: copyfiles.xml vs 64-bit builds
copyfiles.xml contains a hardcoded list of file names.

Some files such as krb5_32.dll and krb5_32.lib have different names when
building for 64-bit. For example, krb5_64.dll and krb5_64.lib.

Some files, such as the Kerberos v4 library are never installed on
64-bit systems and will not be installed in future 32-bit builds.

When constructing the staging area from copyfiles.xml, the copy will
fail because files that are not built are not found.

One possible approach to address this: Add an additional property to
the File entries specifying component names and then selectively enable
or disable components by the CPU type of the build.
Subject: RE: [krbdev.mit.edu #5819] copyfiles.xml vs 64-bit builds
Date: Wed, 24 Oct 2007 14:24:47 -0400
From: "Danilo Almeida" <dalmeida@centeris.com>
To: <rt@krbdev.mit.edu>
RT-Send-Cc:
Why change the filenames for the 64-bit builds? 64-bit windows still uses kerbel32.dll, etc for the 64-bit components?

- Danilo
Date: Wed, 24 Oct 2007 15:19:50 -0400
From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #5819] copyfiles.xml vs 64-bit builds
RT-Send-Cc:
Danilo Almeida via RT wrote:
Show quoted text
> Why change the filenames for the 64-bit builds? 64-bit windows still uses kerbel32.dll, etc for the 64-bit components?
>
> - Danilo
So they can be installed in the same directory. It was something that
was desired by MIT when we started the 64-bit port several years ago.
Download smime.p7s
application/x-pkcs7-signature 3.2KiB

Message body not shown because it is not plain text.