On 27/01/15 10:45, Martin Lucina wrote: > Hi, > > The current names used for platform macros, app-tools and the configure > vendor string have over time become inconsistent with the naming of the > rumprun stack.
A third naming by a third person should be the charm ;) > In rumprun-xen, the current situation is: > > Platform macros: -D__RUMPUSER_XEN__ -D__RUMPAPP__ -D__NetBSD__ > app-tools: rumpapp-xen-* > autoconf vendor string: $ARCH-rumpxen-netbsd > > As people are now starting to depend on these in code/build systems, I > propose to rename them as follows: > > Platform macros: -D__RUMPRUN__ -D__NetBSD__ > app-tools: rumprun-xen-* > autoconf vendor string: $ARCH-rumprun-netbsd > > At Antti's suggestion, I've dropped the Xen-specific platform macro - does > anyone foresee a need for keeping it? I suggested thinking critically about if it's necessary. Now that I look at your list, the same goes for the autoconf vendor string. Actually, the autoconf string is in need of even more critical thinking, since we can always add -D__RUMPRUN_XEN__ later, but if there's some case where need "xen" in the autoconf string, we're out of luck. That said, I'd prefer to see just a generic rumprun identifier in both cases, if critical thinking does not yield other results. While you're renaming, should we start calling app-tools rumprun-tools? ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
