On 22 October 2012 03:48, Kent A. Reed <[email protected]> wrote:
> Well, when I directly invoke "comp" on a file in the working directory, > it leaves the resulting .c file in the same working directory. Yes, that is a third special case :-) I have a feeling that comp --install puts the temporary C-file in the modules directory where the .ko will end up and then deletes it. If this is the case then in the unlikely situation where one had the source tree but wanted to compile into an installed system then there might be a 4th place that the .c file might end up. > Considering the quick-n-dirty test I just did with mesa_7i65.comp, a > comp "include" command before the ;; delimiter appears simply to be > quoted into the resulting .c file with an appropriate leading "#" > prepended to it. Not very mysterious and consistent with what I said > above Indeed, though that is still rather useful as it puts the #include early in the source code, whereas after the ;; is often much too late. -- atp If you can't fix it, you don't own it. http://www.ifixit.com/Manifesto ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
