|
From: Nicholas N. <nj...@cs...> - 2005-02-27 17:36:30
|
On Sun, 27 Feb 2005, Jeroen Ruigrok/asmodai wrote: > Given I am extending the code base for DragonFly support (and if I can > manage some other BSDs as well) I am encountering some things. Good to hear. What is DragonFly exactly? Looks like a FreeBSD fork designed to handle multi-processor/clustered systems well? Does the world really need another BSD? :) BTW, I assume you're working off the CVS HEAD, rather than 2.2.0? If not, you should be, there have been big changes since 2.2.0 that should make your life much easier. > configure.in: > > AC_OUTPUT( > [snip...] > include/x86/Makefile > include/linux/Makefile > include/x86-linux/Makefile > [snip...] > ) > > I thought about doing linux -> $VG_OS and x86-linux -> $VG_PLATFORM, but of > course automake does not like this, since it doesn't know about $VG_OS or > $VG_PLATFORM since that's set at runtime by configure. > > Any ideas/suggestions about this? Since it seems a bit awkward to create > all Makefiles for all OSes and targets when only one combination should > suffice. I wouldn't worry about it. The disadvantage of it is that it causes the distro to use some extra disk space, and it requires a tiny amount of extra time for those running configure.in. These aren't very important. The big advantage of doing it this way is that the code tree you have after running autoconf will work for any platform, which seems to me like a very good thing. If we one day support hundreds of platforms and it becomes a problem, we can do something about it then :) N |