[EMAIL PROTECTED] wrote: > Hello list, > > Currently, Xenomai/SOLO comes with testsuite for VxWorks emulation. > The path to Xenomai/SOLO installation is fixed. The patch attempts to > obtain the proper prefix during build process. > > Regards, > -jserv > > diff --git a/vxworks/testsuite/Makefile b/vxworks/testsuite/Makefile > index 62430ff..13ca9a0 100644 > --- a/vxworks/testsuite/Makefile > +++ b/vxworks/testsuite/Makefile > @@ -1,4 +1,4 @@ > -SOLO := /usr/local/solo > +SOLO := $(shell sed -n '/^prefix/'p ../Makefile | cut -c 9-) > XENO_CONFIG=$(SOLO)/bin/xeno-config > prefix := $(shell $(XENO_CONFIG) --prefix) >
This won't work if you build out of the source tree like autoconf/automake recommend, since it won't find the instantiated Makefile in the upper directory. We could use an autoconf template to patch the prefix into testsuite/Makefile.in, but the testsuite/ directory is meant to be movable and compilable anywhere the user sees fit. This is basically why the Makefile has not been autoconfiscated in the first place. I guess we will have to leave with the "set your Xenomai install directory for scripts and binaries in your PATH variable" rule. I have removed the absolute SOLO prefix from the Makefile though, it was a left over from my development environment. Thanks for spotting this. -- Philippe. _______________________________________________ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core