On Sun, Feb 6, 2011 at 2:20 AM, john skaller <[email protected]> wrote: > > Generating code in a build system is fraught with difficulties. > Such as "using make" or "using bash" to do it. Such as finding out > which compiler to use to actually build the tool that generates the > code. Best not to get into this! [Felix does it, but we have spent several > years developing portable technology to do it, written in Python] > > This is also what GNU tends to do. Although code generators are included > in the repository, so is the code it generates. In particular, "automake" can > be used to generate makefiles, but this is done by the original developer, > not the client. > > You can get our version from GitHub as erickt/judy [I'll leave it to Erick to > provide the details]
Hey John, I have already partially modified felix's build system to compile judy straight from a tarball, so we won't have to deal with copying files around. I put it off until after we cut our next release since at the time it sounded like we were ding that soon. I'll see if I can finish it up over the next couple days. Judy folks, I'm not sure if you'd be interested, but I'd be happy to take my changes and make an independent build system using our fbuild (http://github.com/erickt/fbuild) if anyone's interested. ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Judy-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/judy-devel
