| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Epics configure Makefile generation |
| From: | Jeong Han Lee via Core-talk <[email protected]> |
| To: | Heinz Junkes <[email protected]> |
| Cc: | [email protected] |
| Date: | Sat, 14 Sep 2019 01:41:41 +0200 |
Hi HeinzI don't think I understand your question fully, but the following way I recently implemented a makefile rule into ESS EPICS building system to identify many variables. I've found it from the reference [1] such as
print-%: @echo $* = $($*) @echo $*\'s origin is $(origin $*) You can add them into your makefile rule, then it returns $ make print-EPICS_VERSION_STRING EPICS_VERSION_STRING = EPICS Version 7.0.3 EPICS_VERSION_STRING's origin is file I hope this may match your question. Best, Han [1] https://www.cmcrossroads.com/article/printing-value-makefile-variable On 9/13/19 5:24 PM, Heinz Junkes via Core-talk wrote:
It was more of a general question how to simple debug the "make”. These .rel entries no longer exist for my RTEMS5: ... #-------------------------------------------------- # Operating system flags ifneq ($(RTEMS_SERIES),5) OP_SYS_LDLIBS += -lrtemsCom -lc -lrtemscpu -lCom -lnfs -lm endif ifeq ($(RTEMS_SERIES),5) OP_SYS_LDLIBS += -lrtemsCom -lnfs -ltftpfs endif OP_SYS_LDFLAGS_posix += -u POSIX_Init OP_SYS_LDFLAGS_kernel += -u Init \ $(PROJECT_RELEASE)/lib/no-dpmem.rel \ $(PROJECT_RELEASE)/lib/no-mp.rel \ $(PROJECT_RELEASE)/lib/no-part.rel \ $(PROJECT_RELEASE)/lib/no-signal.rel \ $(PROJECT_RELEASE)/lib/no-rtmon.rel OP_SYS_LDFLAGS += $(CPU_CFLAGS) $(OP_SYS_LDFLAGS_$(OS_API)) ... Viele Grüße Heinz Junkes -- Experience directly varies with equipment ruined.On 13. Sep 2019, at 17:16, Michael Davidsaver <[email protected]> wrote: On 9/13/19 3:15 AM, Heinz Junkes via Core-talk wrote:I need to create a reasonable configure/os/CONFIG.Common.RTEMS-mvme2500 Is there a simple debug possibility to follow or test the generation of flags like OP_SYS_LDFLAGS etc.?Are you asking about the .rel entries in configure/os/CONFIG.Common.RTEMS ?OP_SYS_LDLIBS += -lrtemsCom -lc -lrtemscpu -lCom -lnfs -lm OP_SYS_LDFLAGS += $(CPU_CFLAGS) -u Init \ $(PROJECT_RELEASE)/lib/no-dpmem.rel \ $(PROJECT_RELEASE)/lib/no-mp.rel \ $(PROJECT_RELEASE)/lib/no-part.rel \ $(PROJECT_RELEASE)/lib/no-signal.rel \ $(PROJECT_RELEASE)/lib/no-rtmon.relI have occasionally wondered what when into selecting them, though unfortunately never long enough to dig through the RTEMS documentation.