1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 <2013> 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 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: registerRecordDevice... crashes IOC during startup |
From: | Dirk Zimoch <[email protected]> |
To: | [email protected] |
Date: | Mon, 01 Jul 2013 10:10:15 +0200 |
On 29.06.2013 19:09, Andrew Johnson wrote:
We don't know at compile-time that you aren't planning to load the xyz module from some other .munch file or lib.so shared library (and although I don't particularly recommend it, that is something which Dirk Zimoch wants to be able to do). Now I could conceive of some kind of optional way to test your binary for completeness(which Dirk would not use), but for VxWorks that would require that we know all of the symbols that your specific VxWorks boot image provides since those are symbols which are supposed to be undefined in your .munch file.
Hi Andrew,That is not exactly what I want to be able to do. I want to be able to build software modular. That still means that the code and the entry in the dbd must match. For example if the dbd mentions registrar(xyz), that registrar should be in the code.
I want to be able to define device support for a record type in a different module than the record itself. I.e. to be able to have the dbd entry for devAiXXX together with the code. But without having to include the aiRecord.dbd into my dbd file. Exactly because my module does not provide the aiRecord code.
Thus I also prefer a system that warns me if I define something in the dbd file that is missing in the code. I simply do not want to put all dependencies into the dbd file, because that forces me to build monolithic code.
Dirk