From: Karri Kaksonen; on Date: October 18, 2004, at 03:00 AM -0400 > > I like the idea of making the building more like other packages. It took > me a while to figure out how to build it in the first place. and for > some reason, even a small modification to the source keeps the build > going on for 15 minutes or so. > > What I expect is to be able to > cd libsrc/lynx > make > > and when that compiles well, I do a > sudo make install > at the top level. > > There may be a way to do that already, but I have not found it yet. I like that style, too. So, I wrote my own GNUmakefiles that work that way. But, Uz doesn't use that style -- at least, not in the library subtree (interestingly, the development tool subtree does work in that autonomous way). You rebuild a single library by starting in the parent subdirectory, and naming that library as a make goal: cd cc65/libsrc; make lynxlib > > Currently, I do a > sudo make -f make/gcc.mak install > at top level, and get a cup of something while I am waiting. A desire for portability is one of the reasons for the current method. Uz wanted many host systems to be able to build the cc65 package -- DOS-like ones, as well as Unix-like ones. He wants us to be able to modify any file, then update all of the libraries -- for all targets -- without resorting to fancy makefile tricks. [I love to write those tricks -- but, I'm weird. ;-) ] ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Tue Oct 19 05:45:22 2004
This archive was generated by hypermail 2.1.8 : 2004-10-19 05:45:32 CEST