使用 nant 构建城堡项目时,构建日志在哪里?

发布于 2024-07-22 13:06:24 字数 1467 浏览 10 评论 0 原文

我正在尝试使用 nant 构建城堡项目并获得以下结尾的输出:

                common.compile-dll:

                      [csc] Compiling 92 files to 'C:\code\OSS\castle\build\net-3.5\release\Castle.Core.dll'.
                      [csc] error CS0006: Metadata file 'System.Core.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Data.DataSetExtensions.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Data.Linq.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.ServiceModel.Web.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Web.Extensions.Design.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Web.Extensions.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Xml.Linq.dll' could not be found

                BUILD FAILED

                C:\code\OSS\castle\common-project.xml(127,5):
                External Program Failed: c:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.exe (return code was 1)

                Total time: 1.1 seconds.


    BUILD FAILED

    Nested build failed.  Refer to build log for exact reason.

现在也许我可以弄清楚这一点,或者至少有一个更合理的问题要问我是否知道构建日志的位置,它通常去哪里? 将 -l 选项添加到 nant 命令会生成包含与屏幕输出完全相同的消息的日志。 有人有什么想法吗?

(有趣的是,这与之前提出的问题完全重复,但没有任何回应而被删除)

I am trying to build castle project using nant and get output ending in the following:

                common.compile-dll:

                      [csc] Compiling 92 files to 'C:\code\OSS\castle\build\net-3.5\release\Castle.Core.dll'.
                      [csc] error CS0006: Metadata file 'System.Core.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Data.DataSetExtensions.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Data.Linq.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.ServiceModel.Web.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Web.Extensions.Design.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Web.Extensions.dll' could not be found
                      [csc] error CS0006: Metadata file 'System.Xml.Linq.dll' could not be found

                BUILD FAILED

                C:\code\OSS\castle\common-project.xml(127,5):
                External Program Failed: c:\WINDOWS\Microsoft.NET\Framework\v3.5\csc.exe (return code was 1)

                Total time: 1.1 seconds.


    BUILD FAILED

    Nested build failed.  Refer to build log for exact reason.

Now maybe I could figure this out or at least have a more legitimate question to ask if I knew the location of the build log, where does it typically go? Adding the -l option to the nant command results in a log containing the exact same message as got output to screen. Anyone have any idea?

(Interestingly this is an exact duplicate of a question that was asked before and deleted with no response)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

眼睛会笑 2024-07-29 13:06:24

您的特定错误似乎与 nant 使用错误的目标框架有关(未检测/使用 net-3.5),请尝试下载最新版本的 nant 来解决问题。

注意:castle项目已迁移github:


对您问题的一些回答:

它通常去哪里?

  • 构建日志转到控制台输出或重定向控制台输出的位置
  • 构建输出转到 ~/build/.NETFramework-v3.5/Release 或 Debug 文件夹(我误读了问题的哪个输出部分)

将 -l 选项添加到 nant 命令会生成包含与屏幕输出完全相同的消息的日志。 大家有什么想法吗?

一般来说,使用 nant,您可以传递详细参数以进行更多诊断,如果您希望将控制台输出到文件,只需添加后缀 > > 文件名.txt

nant -v ... > 详细输出.txt

your particular error seems related to nant working with wrong target framework (didn't detect/use net-3.5), try downloading last version of nant to fix the problem.

note: castle project migrated github:


some answers to your questions:

where does it typically go?

  • build log goes to console output or where console output is redirected
  • build output goes to ~/build/.NETFramework-v3.5/Release or Debug folder (I misread the which output part of your question)

Adding the -l option to the nant command results in a log containing the exact same message as got output to screen. Anyone have any idea?

generaly with nant, you could pass the verbose argument for more diagnostics, if you want tp output the console to a file, simply suffix with > filename.txt

nant -v ... > verboseoutput.txt

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文