[really a question to Seb, but touching wider config issues]
a question about the buildbot: does the build VM actually run the RTAI kernel? or does it just carry the RTAI files so it can build? the issue behind the question is: the current src/configure --with-realtime=<pointing-to-some-script-or-directory> option is really odd, and hard to generalize the approach in debian/configure is much better IMO: it takes 'sim', a given kernel version, or the running kernel's version with '-r' now if you have the target kernel running, you can use 'uname -r' in configure, but if you build on a generic kernel and just say the RTAI libraries and files, then you cant. How do you do this? In the future we might have builds for RTAI, Xenomai, RT_PREEMPT and vanilla, and IMO it would be unwieldy to have a build machine with a matching kernel just for that. I would think realistically the build machine would have all target kernels and RT support files *installed* but just one of them running (doesnt matter which) If it is OK to assume that the build target kernel is *installed* but *not running* and support files in place, then I would go a different route: do the build by specifying a target kernel like in 'debian/configure <kernelversion>' and then investigate the config files in /boot/config-<kernelversion> to find out what the target kernel is about. AFAICT there is no clear method I could think of whether a given kernelversion string is RT_PREEMPT or generic except for looking in /boot/config* . what do you think? -m ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
