You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-user@logging.apache.org by Gert Driesen <ge...@pandora.be> on 2004/09/12 18:54:51 UTC

Re: Build problems with CVS code

Try using a recent nightly build of NAnt : 
http://nant.sourceforge.net/nightly/builds

Gert


----- Original Message ----- 
From: "Shai Berger" <sh...@tase.co.il>
To: <lo...@logging.apache.org>
Sent: Sunday, September 12, 2004 7:51 PM
Subject: Build problems with CVS code


Hi guys,

I'm trying to evaluate log4net for use in a project here, and I encountered 
some problems in the first attempts to build; I hope to get some advice from 
the more experienced folks here.

I checked out the source from CVS, and first tried to build it with NAnt. 
This failed miserably; the latest stable NAnt (0.84) cannot read the build 
files, because the syntax they use for <if/> (test="...") is not (no 
longer?) supported. NAnt expects to see <if propertyexists="...">, and the 
files have <if test="property::exists('...')">. What version of NAnt are 
these files written for? Are the developers aware that the build files don't 
work? Or have I misunderstood something?

Then I found the solution file, and successfully built Log4Net in VS.NET 
2003 (after an automatic conversion of the solution and project files). I 
understand that Log4Net was tested in Framework 1.1, but was it built with 
VS.NET 2003? Should I expect problems?

Also, if I understand correctly, having transformed the project files will 
prevent me from following the development on CVS (at least inasmuch as 
project-file changes are involved). Is there a known solution to this 
problem?

Thanks in advance,

Shai.
**************************************************************************************************
The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only.
If you have received this email in error please notify the system manager or 
the
sender immediately and do not disclose the contents to anyone or make 
copies.

** TASE scanned this email for viruses, vandals and malicious content. **
**************************************************************************************************