logging-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicko Cadell" <ni...@neoworks.com>
Subject RE: [VOTE] publish log4net 1.2.10
Date Wed, 15 Mar 2006 12:20:07 GMT
Ron,

The download contains binaries for all the build targets. It looks like
you didn't clear the /bin directory before doing your first build. This
would have meant that you where building some of the build targets, but
most were not being touched at all and just left with the original
versions from the download.

The release builds are strongly named (where this is supported by the
platform). As you found, without the strong name key file none of
release builds are built.

When you removed the /bin directory and rebuilt you actually saw the
builds you are currently compiling. In order to build the release
versions you need to put back the strong name key. In order to build for
MS .NET 2.0 you need a newer version of NAnt
(http://nant.sourceforge.net/) a nightly build of 0.85 since 2006/03/04
supports the final release of the .NET 2.0 runtime.

To build the Mono and SSCLI build targets you need to install Mono
1.1.13 (http://www.mono-project.com) and SSCLI 1.0
(http://msdn.microsoft.com/library/en-us/dndotnet/html/mssharsourcecli.a
sp). Note you need to build the SSCLI from source.

You can view the frameworks that NAnt has discovered by running:

build.cmd display-setup

Cheers,
Nicko

> -----Original Message-----
> From: Ron Grabowski [mailto:rongrabowski@yahoo.com] 
> Sent: 15 March 2006 01:07
> To: Logging General
> Subject: Re: [VOTE] publish log4net 1.2.10
> 
> I downloaded:
> 
> http://people.apache.org/~nicko/log4net/test-build/incubating-
> log4net-1.2.10.zip
> 
> unzipped it and ran "build.cmd" on my Windows XP system with 
> both 1.1 and 2.0 of the framework installed. This is part of 
> the output from the build.cmd file:
> 
> "
> C:\incubating-log4net-1.2.10>build
> LOG4NET_DIR is C:\incubating-log4net-1.2.10 NANTEXE_PATH is 
> nant.exe BUILD_FILE is C:\incubating-log4net-1.2.10\log4net.build
> NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005) Copyright (C) 
> 2001-2005 Gerry Shaw http://nant.sourceforge.net
> 
> Buildfile: file:///C:/incubating-log4net-1.2.10/log4net.build
> Target framework: Microsoft .NET Framework 1.1
> Target(s) specified: compile-all
> "
> 
> I saw this warning towards the end:
> 
> "
> compile-net-1.1:
> 
>      [echo] Key file not found. You can generate a key file 
> by running 'sn -k lo g4net.snk'.
>      [echo] The generated key file should be stored in the 
> log4net base director y.
> "
> 
> which was caused by me not calling the sn command to generate 
> a key file. This is output of files in the \bin directory:
> 
> C:\incubating-log4net-1.2.10\bin\cli
> C:\incubating-log4net-1.2.10\bin\mono
> C:\incubating-log4net-1.2.10\bin\net
> C:\incubating-log4net-1.2.10\bin\netcf
> C:\incubating-log4net-1.2.10\bin\sscli
> C:\incubating-log4net-1.2.10\bin\cli\1.0
> C:\incubating-log4net-1.2.10\bin\cli\1.0\release
> C:\incubating-log4net-1.2.10\bin\cli\1.0\release\log4net.dll
> C:\incubating-log4net-1.2.10\bin\cli\1.0\release\log4net.xml
> C:\incubating-log4net-1.2.10\bin\mono\1.0
> C:\incubating-log4net-1.2.10\bin\mono\2.0
> C:\incubating-log4net-1.2.10\bin\mono\1.0\debug
> C:\incubating-log4net-1.2.10\bin\mono\1.0\release
> C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.dll.mdb
> C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\mono\1.0\release\log4net.dll
> C:\incubating-log4net-1.2.10\bin\mono\1.0\release\log4net.xml
> C:\incubating-log4net-1.2.10\bin\mono\2.0\debug
> C:\incubating-log4net-1.2.10\bin\mono\2.0\release
> C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.dll.mdb
> C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\mono\2.0\release\log4net.dll
> C:\incubating-log4net-1.2.10\bin\mono\2.0\release\log4net.xml
> C:\incubating-log4net-1.2.10\bin\net\1.0
> C:\incubating-log4net-1.2.10\bin\net\1.1
> C:\incubating-log4net-1.2.10\bin\net\2.0
> C:\incubating-log4net-1.2.10\bin\net\1.0\debug
> C:\incubating-log4net-1.2.10\bin\net\1.0\release
> C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\net\1.0\release\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\1.0\release\log4net.xml
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug
> C:\incubating-log4net-1.2.10\bin\net\1.1\release
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\net\2.0\debug
> C:\incubating-log4net-1.2.10\bin\net\2.0\release
> C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\net\2.0\release\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\2.0\release\log4net.xml
> C:\incubating-log4net-1.2.10\bin\netcf\1.0
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\release
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\sscli\1.0
> C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug
> C:\incubating-log4net-1.2.10\bin\sscli\1.0\release
> C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug\log4net.ildb
> C:\incubating-log4net-1.2.10\bin\sscli\1.0\release\log4net.dll
> 
> I noticed that there weren't any files in this folder:
> 
> C:\incubating-log4net-1.2.10\bin\net\1.1\release
> 
> even though there are files in the other release directories. 
> After creating a log4net.snk file and re-building, the 
> \1.1\release\ folder had the correct (strongly signed) 
> assembly in it. I verified this by dragging it into Reflector.
> 
> I then cleared my \bin\ directory, erased the log4net.snk 
> file, and re-ran build.cmd and noticed that there were less 
> folders created in the bin directory the 2nd time around:
> 
> C:\incubating-log4net-1.2.10\bin\net
> C:\incubating-log4net-1.2.10\bin\netcf
> C:\incubating-log4net-1.2.10\bin\net\1.1
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug
> C:\incubating-log4net-1.2.10\bin\net\1.1\release
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.xml
> C:\incubating-log4net-1.2.10\bin\netcf\1.0
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\release
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.dll
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.pdb
> C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.xml
> 
> Is that suppose to happen?
> 
> --- Curt Arnold <carnold@apache.org> wrote:
> 
> > No tag for source, but did have an identified revision number
> > (383994) for the source in the call for vote.  Is the 
> intent to create 
> > the tag only after the votes by the PMC and Incubator?
> > 
> > MD5 checksum verified.
> > 
> > Nicko's key is not present in http://www.apache.org/dist/logging/
> > KEYS, but was at pgp.mit.edu, people.apache.org:~nicko/.pgpkey and 
> > http://people.apache.org/~henkp/trust/apache.html.
> > 
> > I'd like to hear from one of the other log4net committers that they 
> > were able to reproduce the build (with the exception of 
> timestamps et
> >  
> > al).
> > 
> > 
> 
> 

Mime
View raw message