> -----Original Message----- > From: Kevin Dente [mailto:[EMAIL PROTECTED]] > > That's definitely not the case at my company. We have > dozens of old-style DLLs with import libraries, and we > use a library search path for those as well as system libraries.
Then in the proposed scheme you'd have to list them twice. Once with just a filename to pass to the linker, and once with an entire pathname for the dependencies. Maybe this isn't the best idea in the world, it's just a strawman. But trying to implement the same search algorithm as the linker seems problematic. Do they search in the LIB environment variable first, or after what you specify on the command line? Do they include the current directory? Etc, etc. I can go either way (especially if you're volunteering to implement the harder solution!). Eric. _______________________________________________________________ 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
