2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 <2006> 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: 3.14.8 / cygwin dependency |
From: | Andrew Johnson <[email protected]> |
To: | Ralph Lange <[email protected]> |
Cc: | EPICS Core Talk <[email protected]> |
Date: | Tue, 24 Jan 2006 10:03:57 -0600 |
Ralph Lange wrote:
Now I would say it's generally bad to use wildcards for what is done within make target chains, as this introduces hidden dependencies that make never has a chance to know about and resolve correctly.
In principle I agree with you, although I don't know anything about this specific rule.
Janet (or Jeff): What was this wildcard introduced for? As it's not for the Borland (by ifdef) and not for the Microsoft (by my experience), it can only affect the MinGW or Cygnus compilers. Are there other files generated apart from the target dll or exe? Or does the compiler name the target dll or exe different from the usual make target name? Wouldn't it be possible and more appropriate to add targets or change the target name in that case?
I wonder if it's related to the manifest files, which Ken has just been telling me all about. With the latest MS Visual Studio 8.0 release running on XP (w2k is apparently immune from this), an executable will only run properly if the manifest file that details all the DLLs it needs is installed in the same directory as the executable.
Janet may be a little busy right now as we're coming to the end of a shutdown, but I'm sure she'll respond when she has time.
- Andrew -- * * Matt Santos / / For a Brighter America * *