[syslinux] Keyboard stops working, on the learning curve
stappers at stappers.nl
Tue Jul 26 01:41:13 PDT 2005
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Jul 25, 2005 at 04:13:44PM -0700, Samuel Clements wrote:
> n00b situation two:
> how do I compile in my changes? I'm used to a 'gmake clean' and all
> the usable binaries go away, edit code, gmake (or gmake pxelinux.0) and
> usable binaries come back. When I gmake clean, pxelinux.0 still exists.
> Once I edit files and re-compile them, how do I make sure my changed
> pxelinux.0 file contains the changes I just made?
`make clean` doesn't delete what is build (and shouldn't)
You are looking for `make spotless` to delete items that build.
Other common practice is to use `make really-clean` or `make mrproper`
for the removal of the builded targets. See the makefile to find out
what to use ( it varies from project to project )
Another way to find out that you are actual working with the file
that you build yourself, is to modify a text string. Either a printed
string or one that you get visable with the strings(1) program.
> Thanks in advance. I'll check file size differences for now to see if
> something jumps out at me!
It is nice to see that you like the hacking.
( http://www.catb.org/~esr/faqs/hacker-howto.html )
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Syslinux