Experimental Physics and
Industrial Control System

Heinz Junkes via Core-talk <[email protected]> · Mon, 16 Sep 2019 11:24:45 +0200

Hi Andrew,

Danke,
works …

[junkes@dune libcom (7.0 *)]$ make T_A=RTEMS-qoriq_e500 PRINT.OP_SYS_LDFLAGS
OP_SYS_LDFLAGS =   -mcpu=8540 -meabi -msdata=sysv -fno-common -mstrict-align -mspe -mabi=spe -mfloat-gprs=double -u POSIX_Init

Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.

> On 14. Sep 2019, at 13:58, Johnson, Andrew N. <[email protected]> wrote:
> 
> We already have a rule like that built into Base, but it’s spelled PRINT.varname
> 
> - Andrew
> 
> -- 
> Sent from my iPad
> 
>> On Sep 13, 2019, at 7:42 PM, Jeong Han Lee via Core-talk <[email protected]> wrote:
>> 
>> Hi Heinz
>> 
>> I 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.rel
>>>> 
>>>> I have occasionally wondered what when into selecting them, though unfortunately never
>>>> long enough to dig through the RTEMS documentation.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System