Melchior FRANZ wrote: > I never "make install" in SimGear, but have a link to the simgear dir > from /usr/local/include. This has always worked. But it cannot work > when the source refers to simgear/nasal.h, although the file is > actually in simgear/nasal/nasal.h.
You misunderstand. The build system makes no guarantee that the locations of files in the install tree will match their locations in the source tree. This has always worked only because SimGear has adhered to a convention where this is so. The issue of what the #include lines contain is secondary. The install location needs to be modified in the Makefile.am as well, otherwise you will just break people building from an installed tree. If any automake gurus can tell me how to make the nasal.h header appear in a "nasal" subdirectory, please tell me. :) > No. I find it disgusting. HTML pages with ECMA p*ss me off. They > tend to not work. Browsers have historically implemented standard Javascript APIs like DOM badly. And web developers have historically done a poor job of handling these incompatibilities. None of that has anything to do with the language. You really should take a look. It's quite sane. Obviously, Nasal isn't a browser extension language and has no DOM implementation, so you're safe. :) Andy _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
