I don't quite follow you. Whether or not it's a Microsoft library or one of my own, I still need to detect whether the library has changed and therefore a rebuild is required. For either case I need to search a "library path".
--- Tomas Restrepo <[EMAIL PROTECTED]> wrote: > > Kevin, > > > The problem is not the linker command line - that > > already works. The problem is using Nant to check > > dependencies, so that the task knows if a rebuild > (or > > re-link) is necessary. > > Well, the easy way out would be to distinguish > between those libs that usually don't change (such > as those provided by MS in VS or PSDK), and those > you create in your projects which might change > often. So you could have, perhaps, a "dependencies" > fileset, besides the usual list of libraries to link > to. (Of course, you'd add the libs in "dependencies" > to the linker command line so that they are linked > in, too). This would be similar to how VS does it, I > think... > > -- > Tomas Restrepo > [EMAIL PROTECTED] > > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application > Developer's Conference > August 25-28 in Las Vegas - > http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
