There isn't that much difference for managed binaries - maybe none. Line
number info and a bunch of other stuff is stored in the pdb files and
most optimisations are done at JIT time rather than when generating il.
If you compare file sizes between debug and release they are usually
identical.
Subject: [nant-dev] Windows setup contribution
Hi all.
I always package up NAnt in a setup for my developers so I thought
I could as well contribute the iss script file I use in case there are
more
out there that would like it.
It uses InnoSetup 4.2.0 http://www.jrsoftware.org/isdl.php
[EMAIL PROTECTED]
To: Jaroslaw Kowalski [EMAIL PROTECTED]
Cc: Nicklas Norling [EMAIL PROTECTED]; Nant-Developers (E-mail)
[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 11:44 AM
Subject: Re: [nant-dev] Windows setup contribution
Why not just add an install target to nant.build and have
: Wednesday, March 24, 2004 11:44 AM
Subject: Re: [nant-dev] Windows setup contribution
Why not just add an install target to nant.build and have the current
make file call it. So you could just do:
make install prefix=/usr/local
actually come to think of it NAnt shouldn't put all its binaries
Hi all.
I always package up NAnt in a setup for my developers so I thought
I could as well contribute the iss script file I use in case there are more
out there that would like it.
It uses InnoSetup 4.2.0 http://www.jrsoftware.org/isdl.php which is a totaly
free and awsome setup tool.
The iss
-Developers (E-mail) [EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 4:10 PM
Subject: [nant-dev] Windows setup contribution
Hi all.
I always package up NAnt in a setup for my developers so I thought
I could as well contribute the iss script file I use in case there are
more
out there that would like
be the NAnt-NDoc documenters, right?
- Original Message -
From: Jaroslaw Kowalski [EMAIL PROTECTED]
To: Nicklas Norling [EMAIL PROTECTED]; Nant-Developers (E-mail)
[EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 9:29 AM
Subject: Re: [nant-dev] Windows setup contribution
Very nice installer
Very nice installer!
I have some ideas for 1.0 release and I wonder if they can all be
implemented with this tool:
1. Binaries should go to Program Files\NAnt\bin and should include
*.exe,
*.dll but no *.xml (at least not by default)
2. I wonder if we could get rid of the *.pdb since they
http://www.jrsoftware.org/isfaq.php has a section on changing environment
variables (like the path).
I've seen it, but I want more. The package made today can be upgraded by
simply installing over an existing installation. Then I don't want the PATH
to
get the Nant dir added again, and again...
Yes, for a release we should not dist the pdb files.
That's a effect of the release being built in debug config. Maybe a release
should
not be debug built? I must say I actually don't really know if there is any
particular
differance. For fun I sometimes recompile the release with release config
- Original Message -
From: Nicklas Norling [EMAIL PROTECTED]
To: Scott Hernandez [EMAIL PROTECTED]; Jaroslaw Kowalski
[EMAIL PROTECTED]
Cc: Nant-Developers (E-mail) [EMAIL PROTECTED]
Sent: Tuesday, March 23, 2004 7:15 PM
Subject: Re: [nant-dev] Windows setup contribution
Yes
Yes, for a release we should not dist the pdb files.
That's a effect of the release being built in debug config. Maybe a
release
should
not be debug built?
The 0.84 release was definitely not built in debug mode (and as a result
does not contain the debug files).
That's our Gert! I
12 matches
Mail list logo
