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.
--- Tomas Restrepo <[EMAIL PROTECTED]> wrote: > Hi Kevin, > > > Has anybody else had a requirement like this? Is > there > > some other way to accomplish my goal? Can the > fileset > > be extended to support this? > > I think FileSets would be the wrong structure to use > for this. What I'd like to have for something like > this is an implementation of Ant's FileLists, which > seem appropriate for these kind of things. > > Once I had a FileList, I'd add an attribute to the > link task that specified the library include paths. > Then, generating the command line for the task would > be fairly easy. (after all, the linker already has > the code necessary to search for the library once it > has the include paths... no use reimplementing it on > nant, 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
