Because the libbsd stack does not support some things yet (e.g. ntp) I have to call different functions at rtems_init in EPICS. Therefore, when building EPICS for a target, I need to know which stack the target was built with.
Viele Grüße Heinz Junkes -- Experience directly varies with equipment ruined. > On 4. Aug 2020, at 15:44, Joel Sherrill <j...@rtems.org> wrote: > > > > On Tue, Aug 4, 2020 at 8:10 AM Heinz Junkes <jun...@fhi-berlin.mpg.de> wrote: > I'm trying to figure out when compiling a third party software (EPICS), > whether the RTEMS for a target bsp was created with the legacy stack or > uses the libbsd stack. > > Unfortunately I have found some different definitions: > > in target.cfg : RTEMS_HAS_NETWORKING > in bsp.cfg : HAS_NETWORKING > in header files #if defined(RTEMS_NETWORKING) > > Which one should I take best? > > I tend to RTEMS_HAS_NETWORKING in target.cfg ;-) > > rtems/score/cpuopts.h defines it in the installed headers. but > I think either bsp.cfg or target.cfg would be trustworthy. target.cfg > has more info in it. > > This doesn't help you know before building which network stacks > a BSP supports though. > > --joel > > > Danke Heinz_______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
