Thanks; I think I'll do that.
- Julian
David Megginson wrote:
>
> Julian Foad writes:
>
> > Doesn't everyone have the same problem that I have: that after
> > re-building plib and/or SimGear, even after a one-file change, the
> > "make install" copies all of the header files to the install
Curtis L. Olson wrote:
> This is off the top of my head with a healthy mix of speculation.
> But, I believe you can override the 'install' command in the
> Makefiles. Often it is just "cp" or the is often an actual "install"
> program or similar "install.sh" script. This means that in theory,
>
This is off the top of my head with a healthy mix of speculation.
But, I believe you can override the 'install' command in the
Makefiles. Often it is just "cp" or the is often an actual "install"
program or similar "install.sh" script. This means that in theory,
you ought to be able to write a s
Julian Foad writes:
> Doesn't everyone have the same problem that I have: that after
> re-building plib and/or SimGear, even after a one-file change, the
> "make install" copies all of the header files to the install
> directory, putting the current date stamp on them, even though they
> hav
Doesn't everyone have the same problem that I have: that after re-building plib and/or
SimGear, even after a one-file change, the "make install" copies all of the header
files to the install directory, putting the current date stamp on them, even though
they have not changed. This causes almos
