* change the way include works so that when
tasks/targets execute from
included files the base directory for those tasks
will be relative to the
directory of the included build file.
I actually expect things to work the other way. We use
the include task to provide common targets, in an
True - but then you actually need the IDE installed on
that machine. With the CSPROJ task, you only need the
free C# compiler (as in, you don't need a VS.Net
license for your build machine).
The devenv task is really just the exec task.
--- Brad Wilson [EMAIL PROTECTED] wrote:
Kevin Dente
VS.Net to create the project, the
builder wouldn't need it to perform the build.
I also suspect that the actually build would be faster
than an DEVENV task, since you don't need to launch
the rather beastly IDE.
--- Brad Wilson [EMAIL PROTECTED] wrote:
Kevin Dente wrote:
True - but then you
. Are there any others that make sense?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin
Dente
Sent: Thursday, June 27, 2002 11:54 AM
To: Scott Hernandez
Cc: 'Nant developer's list'
Subject: RE: [nant-dev] Calling
I went ahead and made the changes to the VB6 task so
that it parses the VBP to build its dependency list
(both sources and references). It now pulls its output
file name from the VBP file as well. I'll submit the
change when I submit the others.
--- Ian MacLean [EMAIL PROTECTED] wrote:
Kevin
). So I
changed it such that if the output attribute isn't
set, it gets it from the project. Otherwise, the
attribute setting overrides the project setting.
--- Ian MacLean [EMAIL PROTECTED] wrote:
Kevin Dente wrote:
I went ahead and made the changes to the VB6 task
so
that it parses the VBP
Is it really
that hard to write the paths with the correct case?
Well...at the risk of sounding incredibly lazy or
anal...yes, it is kind of a pain. I've been building
NAnt files for a variety of projects and making sure
that I match case really has been a pain.
On the more philosophical
be the goal. The behavior should be definable
from the operating
system and file system.
The config file could force a behavior, but I think
the default behavior
should be good.
Kevin, what is your P/Invoke method for detection?
-Original Message-
From: Kevin Dente
Oops, I suggested the exact same thing before I had
read this. Serves me right for not reading the whole
thread before replying.
In looking through the Ant code, the only tricky thing
they do is to ensure that there isn't a circular
reference. Not a hard check to do, but an important
one.
---
A while back there were discussions on a couple of
features in NAnt. They were:
* Case sensitivity in filesets
* Configurable properties (property values fetched
from nant.config).
Was a final determination ever made on either of these
issues? Personally, I'm finding case-sensitivity to be
a big
-
[EMAIL PROTECTED]] On Behalf Of Kevin
Dente
Sent: Monday, June 24, 2002 11:55 AM
To: Nant developer's list
Subject: [nant-dev] Old business
A while back there were discussions on a couple of
features in NAnt. They were:
* Case sensitivity in filesets
I assume you are talking
this
should go into the NAnt
core or NAntContrib? I'm leaning towards core.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin
Dente
Sent: Monday, June 17, 2002 11:08 AM
To: Scott Hernandez;
[EMAIL PROTECTED]
Cc: [EMAIL
to the foreach. It
would need to be embedded, or referenced. Right now
a Target is the only
reference-able type.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:nant-developers-
[EMAIL PROTECTED]] On Behalf Of Kevin
Dente
Sent: Monday, June 24, 2002 1:53 PM
To: Scott
I actually kinda like foreach.
--- Scott Hernandez [EMAIL PROTECTED] wrote:
I'm open for suggestions on a better name. :)
-Original Message-
From: Tomas Restrepo
[snip]
That's great! In the general sense, I think this
is much useful,
particularly as we could use it as a
Ah, oops, gotcha. OK, I'll agree with you on that one.
:)
--- Tomas Restrepo [EMAIL PROTECTED] wrote:
Hi Kevin,
I actually kinda like foreach.
Me too. I was referring, however, to
TaskWithEmbeddedTasks, not foreach ;)
--
Tomas Restrepo
[EMAIL PROTECTED]
.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
On
Behalf Of Kevin Dente
Sent: Thu, June 20, 2002 11:31 AM
To: Nant developer's list
Subject: [nant-dev] FileSet includes question
The (now out of date) Nant documentation on the
sourceforge site
Has anybody looked at adding the id/idref of Ant to
NAnt? It's looking to me like very useful feature.
For those who aren't familiar with it, Ant let's you
assign ids to certain elements (like FileSets,
DirSets, FileLists, etc), and then reference those in
other build files. I can definitely see
The (now out of date) Nant documentation on the
sourceforge site for the FileSet says the following
about the includes element:
comma-separated list of patterns of files that must
be included
I read this to mean that a single include tag can
have multiple, comma-separated files/patterns in a
I can't really speak in general, but for the link task
specifically, I'm actually working on adding in
dependency checks right now (cl task also). The C++
stuff isn't quite as evolved as the other compiler
tasks at the moment.
--- John Lam [EMAIL PROTECTED] wrote:
I'm curious - why aren't there
I'm trying to make some changes to the link task (C++
linker), and am struggling with something. What I'm
trying to do is specify a fileset of library files
that should be linked into the EXE, and be able to
search a set of directories to find the library files.
This is of course a fairly typical
I've ever specified anything other than a
system-like library using a
lib search path. For all of my user sorts of
libraries, I always
specify the complete path name.
That's definitely not the case at my company. We have
dozens of old-style DLLs with import libraries, and we
use a
Oh, I see what you're saying. I guess that would work
as long as we only have one lib directory for our lib
files. Hmm, I'll think about that. In the past we've
used the notion of local and network lib paths, to
make local development easier, which we'd have to give
up.
I think I can also code
22 matches
Mail list logo
